From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ryan Hsu <ryanhsu@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k: ath10k: bump up FW API to 6
Date: Thu, 20 Apr 2017 08:52:00 +0000 [thread overview]
Message-ID: <87fuh35umo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8a9bab5f36e8456bafa8d872012bcf3a@euamsexm01a.eu.qualcomm.com> (Kalle Valo's message of "Wed, 19 Apr 2017 16:07:07 +0200")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> ryanhsu@qti.qualcomm.com wrote:
>> From: Ryan Hsu <ryanhsu@qca.qualcomm.com>
>>=20
>> For QCA6174 hw3.0, since WLAN.RM.4.4-00022-QCARMSWPZ-2, it starts to
>> support the board ID information from otp, with some devices released on
>> the market that didn't calibrated with OTP, will have 0 for board ID
>> information, which cause the backward compatibility issue and was fixed
>> in commit 'd2e202c06ca4 ("ath10k: ignore configuring the incorrect board=
_id")'
>>=20
>> So bump the fw api version to differentiate the latest firmware support.
>>=20
>> Signed-off-by: Ryan Hsu <ryanhsu@qca.qualcomm.com>
>
> Patch applied to ath-next branch of ath.git, thanks.
>
> aad1fd7f7677 ath10k: bump up FW API to 6
And I renamed the RM.4.4 firmware image also:
https://github.com/kvalo/ath10k-firmware/commit/da1564dafe1c8175faf694482d1=
649f56229ae96
--=20
Kalle Valo=
prev parent reply other threads:[~2017-04-20 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 21:04 [PATCH] ath10k: ath10k: bump up FW API to 6 ryanhsu
2017-04-19 14:07 ` Kalle Valo
2017-04-20 8:52 ` Kalle Valo [this message]
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=87fuh35umo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ryanhsu@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).