From: Kalle Valo <kvalo@codeaurora.org>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: ath9k-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4] ath9k_htc: introduce support for different fw versions
Date: Fri, 18 Sep 2015 10:42:41 +0300 [thread overview]
Message-ID: <87fv2crx5a.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1441537741-11846-1-git-send-email-linux@rempel-privat.de> (Oleksij Rempel's message of "Sun, 6 Sep 2015 13:09:01 +0200")
Oleksij Rempel <linux@rempel-privat.de> writes:
> Current kernel support only one fw name with theoretically only one
> fw version located in “firmware/htc_[9271|7010].fw”. Which is ok so far we
> have only one fw version (1.3). After we realised new fw 1.4, we faced
> compatibility problem which was decided to solve by firmware name and
> location:
> - new firmware is located now in
> firmware/ath9k_htc/htc_[9271|7010]-1.4.0.fw
> - old version 1.3 should be on old place, so old kernel have no issues
> with it.
> - new kernels including this patch should be able to try different
> supported (min..max) fw version.
> - new kernel should be able to support old fw location too. At least for
> now.
>
> At same time this patch will add new module option which should allow user
> to play with development fw version without replacing stable one. If user
> will set “ath9k_htc use_dev_fw=1” module will try to find
> firmware/ath9k_htc/htc_[9271|7010]-1.dev.0.fw first and if it fails, use
> stable version: for example...1.4.0.fw.
>
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
Thanks, applied manually. You forgot to CC linux-wireless and hence
patchwork didn't see this.
In the future please add a changelog when sending new versions of a
patch.
--
Kalle Valo
next parent reply other threads:[~2015-09-18 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441537741-11846-1-git-send-email-linux@rempel-privat.de>
2015-09-18 7:42 ` Kalle Valo [this message]
2015-09-18 9:50 ` [PATCH v4] ath9k_htc: introduce support for different fw versions Oleksij Rempel
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=87fv2crx5a.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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).