From: Kalle Valo <kvalo@kernel.org>
To: Yanase Yuki <dev@zpc.sakura.ne.jp>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA9984 hw1.0: Add NEC Platforms WG2600HP3 specific BDFs
Date: Fri, 21 Jan 2022 16:07:43 +0200 [thread overview]
Message-ID: <87r1919o7k.fsf@kernel.org> (raw)
In-Reply-To: <20200711093201.GA1053@dev-email> (Yanase Yuki's message of "Sat, 11 Jul 2020 18:35:34 +0900")
Yanase Yuki <dev@zpc.sakura.ne.jp> writes:
> These files are NEC Platforms WG2600HP3 specific BDFs extracted
> from stock firmware.
>
> Required information:
>
> * description for what hardware this is:
> - it is a IPQ8062 based board
> - one QCA9984 radio is used as 2.4GHz radio
> - one QCA9984 radio is used as 5GHz radio
>
> * origin of the board files
> - extracted from stock firmware
>
> * ids to be used with the board files
> - bus=pci,bmi-chip-id=0,bmi-board-id=3,variant=NEC-Platforms-WG2600HP3
> - md5sum: c2cca25e45ba07320ecf4a4b16b9a9bc
> - sha1sum: 0a8f6701fc4654efe67bd3af897a77208c0434c7
> - bus=pci,bmi-chip-id=0,bmi-board-id=4,variant=NEC-Platforms-WG2600HP3
> - md5sum: a552038db2da69a9e91e38e607cceb56
> - sha1sum: de70d1dba9bb40c96ca1c26d85f839d024867a83
Thanks, added to QCA9984/hw1.0/board-2.bin:
New:
bus=pci,bmi-chip-id=0,bmi-board-id=3,variant=NEC-Platforms-WG2600HP3
bus=pci,bmi-chip-id=0,bmi-board-id=4,variant=NEC-Platforms-WG2600HP3
Changed:
Deleted:
2 board image(s) added, 0 changed, 0 deleted, 18 in total
https://github.com/kvalo/ath10k-firmware/commit/43ebf8e2b0b3b9a8c9e79a967c6dc5b6b9eba7ad
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2022-01-21 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 9:35 ath10k-firmware: QCA9984 hw1.0: Add NEC Platforms WG2600HP3 specific BDFs Yanase Yuki
2022-01-21 14:07 ` 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=87r1919o7k.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=dev@zpc.sakura.ne.jp \
/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