From: Kalle Valo <kvalo@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA9984 hw1.0: Add Edgecore-ECW5410-L specific BDFs
Date: Mon, 20 Mar 2023 07:58:19 +0200 [thread overview]
Message-ID: <877cvchslg.fsf@kernel.org> (raw)
In-Reply-To: <6414891b.5d0a0220.6f9f5.e092@mx.google.com> (Christian Marangi's message of "Fri, 17 Mar 2023 16:36:58 +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 IPQ806X based board
> - one QCA9984 radio is used as 2.4GHz radio
> - one QCA9984 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)
>
> - QCA4019 hw1.0
>
> + bus=pci,bmi-chip-id=0,bmi-board-id=1,variant=Edgecore-ECW5410-L
> sha256sum:
> add8a7574c1bce2fedc43fdd69825510be68096aac86c5ef3e5bbd438ff18295
> + bus=pci,bmi-chip-id=0,bmi-board-id=2,variant=Edgecore-ECW5410-L
> sha256sum:
> 9786e70bcb62480d24ff8c5801fa1f211fe78eaf217566b4742b475b4034f4f1
>
> * 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")
I'll drop this one as there's v2.
--
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 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 15:36 ath10k-firmware: QCA9984 hw1.0: Add Edgecore-ECW5410-L specific BDFs Christian Marangi
2023-03-20 5:58 ` 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=877cvchslg.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