From: Sven Eckelmann <sven@narfation.org>
To: Kalle Valo <kvalo@kernel.org>, Josh Boyer <jwboyer@kernel.org>,
ath10k@lists.infradead.org
Cc: Linux Firmware <linux-firmware@kernel.org>,
ath10k@lists.infradead.org,
Linux Wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>,
Christian Lamparter <chunkeey@gmail.com>
Subject: Re: [PATCH v2 1/5] ath10k: QCA4019 hw1.0: update board-2.bin
Date: Sat, 26 Feb 2022 17:59:09 +0100 [thread overview]
Message-ID: <28878626.nLntd5uNke@ripper> (raw)
In-Reply-To: <fa37099b-4d5b-7265-888c-fae3f48f6e9a@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]
On Saturday, 26 February 2022 17:39:23 CET Christian Lamparter wrote:
> The current situation is: OpenWrt has those board files (as ~40 separate
> files) all lined up in:
> <https://github.com/openwrt/openwrt/tree/master/package/firmware/ipq-wifi>
> Once the board-2.bin in linux-firmware.git is updated and a new release is
> made, those files can simply be deleted.)
Minor remark about the OpenWrt part: Keep in mind that some of these files are
newer than the ones in Kalle's repository because the " Update ... BDFs" mails
were not yet processed. I haven't checked all of them but it seems to be at
least the case for the PA1200 BDFs. [1]
Kind regards,
Sven
[1] https://lore.kernel.org/all/2931430.FNKZsP7sFK@sven-l14/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Kalle Valo <kvalo@kernel.org>, Josh Boyer <jwboyer@kernel.org>,
ath10k@lists.infradead.org
Cc: Linux Firmware <linux-firmware@kernel.org>,
ath10k@lists.infradead.org,
Linux Wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>,
Christian Lamparter <chunkeey@gmail.com>
Subject: Re: [PATCH v2 1/5] ath10k: QCA4019 hw1.0: update board-2.bin
Date: Sat, 26 Feb 2022 17:59:09 +0100 [thread overview]
Message-ID: <28878626.nLntd5uNke@ripper> (raw)
In-Reply-To: <fa37099b-4d5b-7265-888c-fae3f48f6e9a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Saturday, 26 February 2022 17:39:23 CET Christian Lamparter wrote:
> The current situation is: OpenWrt has those board files (as ~40 separate
> files) all lined up in:
> <https://github.com/openwrt/openwrt/tree/master/package/firmware/ipq-wifi>
> Once the board-2.bin in linux-firmware.git is updated and a new release is
> made, those files can simply be deleted.)
Minor remark about the OpenWrt part: Keep in mind that some of these files are
newer than the ones in Kalle's repository because the " Update ... BDFs" mails
were not yet processed. I haven't checked all of them but it seems to be at
least the case for the PA1200 BDFs. [1]
Kind regards,
Sven
[1] https://lore.kernel.org/all/2931430.FNKZsP7sFK@sven-l14/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-26 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 19:53 [PATCH v2 1/5] ath10k: QCA4019 hw1.0: update board-2.bin Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 2/5] ath10k: QCA9888 hw2.0: " Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 3/5] ath10k: QCA9984 hw1.0: " Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 4/5] ath10k: QCA99X0 hw2.0: replace board.bin, add updated board-2.bin Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 5/5] ath10k: QCA6174 hw3.0: update board-2.bin Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-24 20:24 ` [PATCH v2 1/5] ath10k: QCA4019 hw1.0: " Josh Boyer
2022-02-24 20:24 ` Josh Boyer
2022-02-26 13:24 ` Kalle Valo
2022-02-26 13:24 ` Kalle Valo
2022-02-26 16:39 ` Christian Lamparter
2022-02-26 16:39 ` Christian Lamparter
2022-02-26 16:59 ` Sven Eckelmann [this message]
2022-02-26 16:59 ` Sven Eckelmann
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=28878626.nLntd5uNke@ripper \
--to=sven@narfation.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@gmail.com \
--cc=jwboyer@kernel.org \
--cc=kvalo@kernel.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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.