From: Kalle Valo <kvalo@codeaurora.org>
To: Tom Psyborg <pozega.tomislav@gmail.com>
Cc: linux-firmware@kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
Adrian Chadd <adrian@freebsd.org>
Subject: Re: [EXTERNAL] [PATCH] ath9k_htc: add fw 1.4.1
Date: Thu, 15 Nov 2018 16:03:27 +0200 [thread overview]
Message-ID: <87h8gibfps.fsf@codeaurora.org> (raw)
In-Reply-To: <CAKR_QVKhAkOq7DydJ2sXBNZOpwmY=6WibOikN5xvehFBVQMMrQ@mail.gmail.com> (Tom Psyborg's message of "Thu, 6 Sep 2018 19:32:41 +0200")
(fixing quotation, PLEASE don't top post)
Tom Psyborg <pozega.tomislav@gmail.com> writes:
>> On 6 September 2018 at 17:32, Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> Tomislav Požega <pozega.tomislav@gmail.com> writes:
>>
>> > Add firmware v1.4.1 that supports up to 8 virtual APs and up
>> > to 16 (current limit, at least on AR9271) client interfaces.
>> > (1 AP + 15 STA, 4 AP + 12 STA etc)
>> >
>> > Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
>> > ---
>> > ath9k_htc/htc_7010-1.4.1.fw | Bin 0 -> 72812 bytes
>> > ath9k_htc/htc_9271-1.4.1.fw | Bin 0 -> 51008 bytes
>> > 2 files changed, 0 insertions(+), 0 deletions(-)
>> > create mode 100644 ath9k_htc/htc_7010-1.4.1.fw
>> > create mode 100644 ath9k_htc/htc_9271-1.4.1.fw
>>
>> Is this is an official release from the open-ath9k-htc-firmware
>> project
>> or just some custom build of yours? I'm asking because I don't see
>> anything in the master branch since January:
>>
>> https://github.com/qca/open-ath9k-htc-firmware/commits/master
>>
>> IMHO Adrian Chadd (CCed) should be the one pushing the ath9k_htc
>> firmware image to linux-firmware, unless the maintainer has
>> changed of
>> course.
>
> I was not sure if the fw images from open-ath9k-htc-firmware project
> are still being pulled into linux-firmware tree, so I created this
> build myself to meet the requirements for one of the patches I sent to
> linux-wireless list.
As ath9k_htc firmere is open it's easy to create backdoors etc and this
is why I think that linux-firmware should not take ath9k_htc firmware
binaries just from anyone, only from maintainers of
open-ath9k-htc-firmware project.
> Adrian, can you push the new fw version via official channel?
Adrian, can you help here?
--
Kalle Valo
next prev parent reply other threads:[~2018-11-15 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 21:53 [PATCH] ath9k_htc: add fw 1.4.1 Tomislav Požega
2018-09-06 15:32 ` [EXTERNAL] " Kalle Valo
[not found] ` <CAKR_QVKhAkOq7DydJ2sXBNZOpwmY=6WibOikN5xvehFBVQMMrQ@mail.gmail.com>
2018-11-15 14:03 ` Kalle Valo [this message]
2018-11-16 20:38 ` Tom Psyborg
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=87h8gibfps.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pozega.tomislav@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.