ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lenski <dlenski@gmail.com>
To: ath10k@lists.infradead.org
Subject: Re: ath10k raw mode
Date: Sat, 22 May 2021 19:18:16 -0700	[thread overview]
Message-ID: <CAOw_LSHOysZvefG0drJDEyQa6wCiZS447eyX42z9P6S5Jjud9A@mail.gmail.com> (raw)
In-Reply-To: <CAOw_LSEjzmUi1KvPM6nyKRV=8N3tqTru-noaKLwE01mcDw6uLg@mail.gmail.com>

On Sat, May 22, 2021 at 7:00 PM Daniel Lenski <dlenski@gmail.com> wrote:
> I'm wondering if there's a firmware file with raw mode enabled for
> QCA9377 (rev 31).
>
> I've tried several firmware versions, and they all appear to be
> similarly lacking in support for raw mode.

I found another message from Nov 2020, which suggests that QCA9377
*did* support monitor mode until… some specific firmware version.
https://lists.infradead.org/pipermail/ath10k/2020-November/012053.html

However, I'm having trouble determining which are the firmware
versions referenced therein, since the commit IDs for linux-firmware
seem to be mistaken.

Does anyone have an idea which are the known-good firmware versions
for monitor/raw mode on QCA9377?
https://github.com/kvalo/ath10k-firmware/commits/master/QCA9377/hw1.0

Thanks,
Dan

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2021-05-23  2:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23  2:00 ath10k raw mode Daniel Lenski
2021-05-23  2:18 ` Daniel Lenski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-08 19:13 Andreas Christoforou
2016-12-09  8:40 ` Michal Kazior
     [not found]   ` <CAPd_300YffoiqezwWx82GuMiSHgC7kg6JCF8KNZ2_ytj=gnfzQ@mail.gmail.com>
2016-12-12 13:33     ` Michal Kazior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOw_LSHOysZvefG0drJDEyQa6wCiZS447eyX42z9P6S5Jjud9A@mail.gmail.com \
    --to=dlenski@gmail.com \
    --cc=ath10k@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).