ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	Robert Marko <robimarko@gmail.com>,
	ath10k@lists.infradead.org, Skorpy <skorpy@darmstadt.ccc.de>
Subject: Re: Update board-2.bin files in linux-firmware
Date: Wed, 10 Oct 2018 14:50:38 +0300	[thread overview]
Message-ID: <87sh1evx4h.fsf@codeaurora.org> (raw)
In-Reply-To: <2515195.qVqrclqyAa@debian64> (Christian Lamparter's message of "Tue, 09 Oct 2018 19:30:18 +0200")

Christian Lamparter <chunkeey@gmail.com> writes:

> On Monday, October 8, 2018 3:04:56 PM CEST Kalle Valo wrote:
>> Christian Lamparter <chunkeey@gmail.com> writes:
>> 
>> > Hello,
>> >
>> > On Friday, September 28, 2018 9:28:44 PM CEST Hauke Mehrtens wrote:
>> >> the ath10k-firmware repository already contains updated board-2.bin
>> >> files with support for more devices. Please also update the board-2.bin
>> >> files shipped in the linux-firmware repository as they are normally
>> >> taken by distributions.
>> >
>> > At this opportunity, I would kindly like to remind the maintainer that there
>> > are currently more pending boardfiles. It would be great if they all could be
>> > included in the next update as well:
>> >
>> > pending
>> > =======
>> >
>> >  * Netgear WAC510
>> >  - https://www.mail-archive.com/ath10k@lists.infradead.org/msg09186.html (IPQ4019)
>> >
>> >  * Netgear Orbi PRO SRK60
>> >  - https://www.mail-archive.com/ath10k@lists.infradead.org/msg09078.html (IPQ4019) 
>> >  - https://www.mail-archive.com/ath10k@lists.infradead.org/msg09079.html (QCA9984)
>> >
>> >  * ZyXEL WRE6606:
>> >  - https://www.mail-archive.com/ath10k@lists.infradead.org/msg08776.html (IPQ4019)
>> >
>> >  * ZyXEL NBG6617:
>> >  - http://lists.infradead.org/pipermail/ath10k/2018-May/011377.html (IPQ4019)
>> >
>> > And there is an update for the ASUS' RT-AC58U
>> >  - http://lists.infradead.org/pipermail/ath10k/2018-January/010770.html (IPQ4019)
>> 
>> Thanks for the list, this was helpful. I should have now added all of
>> these, but the exception ZyXEL WRE6606 for which I couldn't find the
>> actual board files.
> You are right. The two ZyXEL WRE6606 board.bin files were attached to
> first post in the "Add ZyXEL WRE6606 specific BDFs" thread:
> <https://www.mail-archive.com/ath10k@lists.infradead.org/msg08741.html>

Ah, I missed that.

> But sadly not to the response by Magnus Frühling that I linked to.
> How do you want to handle this? Can you take the board bins from:
> <https://www.mail-archive.com/ath10k@lists.infradead.org/msg08741.html>

Yeah, I can take it from the first mail. Thanks again for the help, very
much appreciated.

-- 
Kalle Valo

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

      reply	other threads:[~2018-10-10 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 19:28 Update board-2.bin files in linux-firmware Hauke Mehrtens
2018-09-28 20:04 ` Christian Lamparter
2018-09-29 11:19   ` Kalle Valo
2018-10-08 13:04   ` Kalle Valo
2018-10-09 17:30     ` Christian Lamparter
2018-10-10 11:50       ` 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=87sh1evx4h.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=chunkeey@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=robimarko@gmail.com \
    --cc=skorpy@darmstadt.ccc.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