From: Kalle Valo <kvalo@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA99X0 hw2.0: Add ZTE MF18A specific BDFs (5G)
Date: Mon, 20 Mar 2023 17:52:50 +0200 [thread overview]
Message-ID: <87sfdzfmi5.fsf@kernel.org> (raw)
In-Reply-To: <6415f385.5d0a0220.72099.9555@mx.google.com> (Christian Marangi's message of "Sat, 18 Mar 2023 12:23:40 +0100")
Christian Marangi <ansuelsmth@gmail.com> writes:
> Hi, we have many board file not pused upstream in openwrt. The intention
> is to fix this and have all of them merged.
>
> * description for what hardware this is:
>
> - it is a IPQ4019 based board
> - one QCA99X0 radio is used as 5GHz radio
>
> * origin of the board file (did you create it yourself or where you
> downloaded)
>
> - extracted from the original stock firmware image
>
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
>
> - QCA99X0 hw2.0
>
> + bus=pci,bmi-chip-id=1,bmi-board-id=1.bin,variant=ZTE-MF18A
> sha256sum:
> 409de24fdfa49d8ae11c30b003888749cd93b17fdffc3510c224468cb9584e02
>
> * attach the actual board file (board.bin)
>
> - The name of the files are equal to the id string in the board-2.bin
> (minus the ".bin")
Thanks, added to QCA99X0/hw2.0/board-2.bin:
New:
bus=pci,bmi-chip-id=1,bmi-board-id=1,variant=ZTE-MF18A
Changed:
Deleted:
1 board image(s) added, 0 changed, 0 deleted, 14 in total
https://github.com/kvalo/ath10k-firmware/commit/f876e546ef00ac2b24240ea1da6926a53f269ccc
--
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:[~2023-03-20 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 11:23 ath10k-firmware: QCA99X0 hw2.0: Add ZTE MF18A specific BDFs (5G) Christian Marangi
2023-03-20 15:52 ` 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=87sfdzfmi5.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=ath10k@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox