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:00:13 -0700	[thread overview]
Message-ID: <CAOw_LSEjzmUi1KvPM6nyKRV=8N3tqTru-noaKLwE01mcDw6uLg@mail.gmail.com> (raw)

Hi all,
Apologies for resurrecting a 4.5-year-old thread, but it's the most
relevant one I can find…

On Fri Dec 9 00:40:52 PST 2016, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 8 December 2016 at 20:13, Andreas Christoforou <andreaschristofo@gmail.com> wrote:
> > Dear All,
> >
> > could you please someone send me or let me know where I can download a firmware with raw mode flag enabled for my QCA988X card.
>
> You can check this:
>
>   https://github.com/kvalo/ath10k-firmware/tree/master/QCA988X/hw2.0/10.2.4.70
>
> At the very least 10.2.4.70.54 should support it (at least it does
> advertise it). It probably makes sense to have this (list of raw-mode
> supporting firmware revisions) listed somewhere on
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k - any
> volunteers? :)

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.

- Default firmware as distributed by Ubuntu

  ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5
features ignore-otp crc32 79cea2c7
  ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 93da0176
  ath10k_pci 0000:02:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1

- https://github.com/kvalo/ath10k-firmware/blob/master/QCA9377/hw1.0/WLAN.TF.1.0/firmware-5.bin_WLAN.TF.1.0-00023-QCATFSWPZ-1

  ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.1.0-00023-QCATFSWPZ-1
api 5 features ignore-otp crc32 02fabc07
  ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 93da0176
  ath10k_pci 0000:02:00.0: htt-ver 3.61 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1

- https://github.com/kvalo/ath10k-firmware/blob/master/QCA9377/hw1.0/WLAN.TF.2.1/firmware-6.bin_WLAN.TF.2.1-00021-QCARMSWP-1

  ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1
api 6 features wowlan,ignore-otp crc32 42e41877
  ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 93da0176
  ath10k_pci 0000:02:00.0: Unknown eventid: 3
  ath10k_pci 0000:02:00.0: Unknown eventid: 118809
  ath10k_pci 0000:02:00.0: Unknown eventid: 90118
  ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1

Any chance that there's another one which I'm overlooking, which does
support it?

--
Thanks,
Dan

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23  2:00 Daniel Lenski [this message]
2021-05-23  2:18 ` ath10k raw mode Daniel Lenski
  -- 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_LSEjzmUi1KvPM6nyKRV=8N3tqTru-noaKLwE01mcDw6uLg@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).