From: Kalle Valo <kvalo@codeaurora.org>
To: Cale Collins <ccollins@gateworks.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k_pci rawmode = 1 requires support from firmware
Date: Tue, 24 Mar 2020 14:10:16 +0200 [thread overview]
Message-ID: <87ftdy7y3b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAG2Q2vXt3af3ATRnFNW8bA2BbaQ47fLsS1dL1iJ6JGQg=kbJSQ@mail.gmail.com> (Cale Collins's message of "Fri, 21 Feb 2020 12:26:04 -0800")
Cale Collins <ccollins@gateworks.com> writes:
> When attempting to bring up my mesh0 interface, I recieve an error and
> in "dmesg":
>
> [ 901.629999] ath10k_pci 0001:90:00.0: must load driver with
> rawmode=1 to add mesh interfaces
>
> I enable this mode by changing my bootargs, appending "ath10k_core.rawmode=1".
>
> On boot "dmesg" reports:
>
> [ 12.040581] ath10k_pci 0001:90:00.0: rawmode = 1 requires support
> from firmware
>
> Where does this "supported" firmware come from?
>
> I'm using SparkLAN WPEQ-261ACNI(BT) 802.11ac/abgn + BT PCI Express
> Mini Card (Half) - Qualcomm QCA6174A-5 chipset, with a mainline 4.20.7
> kernel and Ubuntu Bionic root filesystem.
>
> Thank you for looking into this, I'm glad to provide more information if needed.
Not all firmware branches support raw mode. The firmware will have
raw-mode feature bit enabled if it support raw mode, you can check it
like this:
$ ath10k-fwencoder --info firmware-6.bin_WLAN.RM.4.4.1.c3-00059 | grep Features
Features: wowlan,ignore-otp-result,no-nwifi-decap-4addr-padding,raw-mode,mfp-support
For QCA6174 with raw mode I recommend using 4.4.1.c3 branch:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1.c3
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-03-24 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 20:26 ath10k_pci rawmode = 1 requires support from firmware Cale Collins
2020-03-24 12:10 ` Kalle Valo [this message]
2020-03-24 17:39 ` Cale Collins
[not found] <CAG2Q2vUH95JyMqOELtU4=uU3nO5jr2+806KiO+T1-tNdBZ=DYw@mail.gmail.com>
[not found] ` <CAG2Q2vU3spU6VOdGAF5beWmgG1eaWuVm3pc+gzcnhaTUHvX+yw@mail.gmail.com>
[not found] ` <CAMrEMU8DtaKMFqZexurzWZD8iB4YX3CmF7vq2XsaDoD=OC-eoA@mail.gmail.com>
2020-02-26 21:15 ` Cale Collins
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=87ftdy7y3b.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=ccollins@gateworks.com \
/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