From: Kalle Valo <kvalo@kernel.org>
To: <gowhdok@mailfence.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA4019 hw1.0: Add P&W R619AC specific BDFs
Date: Fri, 21 Jan 2022 15:56:17 +0200 [thread overview]
Message-ID: <87tudxb3b2.fsf@kernel.org> (raw)
In-Reply-To: <1357387574.1374587.1636642784281@ichabod.co-bxl> (gowhdok's message of "Thu, 11 Nov 2021 15:59:44 +0100 (CET)")
<gowhdok@mailfence.com> writes:
> Hello,
>
> This is the board files for P&W R619ac, a dual-band wireless router with an IPQ4019 inside.
>
> Relevant pull request on OpenWrt: https://github.com/openwrt/openwrt/pull/3691
>
> The boardfiles are extracted from the stock firmware:
> /lib/firmware/IPQ4019/hw.1/boarddata_0.bin
> /lib/firmware/IPQ4019/hw.1/boarddata_1.bin
>
> The MD5 hashes are consistent with the ones included in the pull request.
>
> ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k):
> - QCA4019 hw1.0
> BoardNames[0]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=P&W R619AC'
> BoardMD5[0]: 05f6d61550d5ba8a0626fb7fa63703fe
>
> BoardNames[1]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=P&W R619AC'
> BoardMD5[1]: 9265da348a1294c326cd0156fd92d0b5
>
> Boardfiles are attached with the appropriate names. You may substitute the & and space with something else saner if they prove to be problematic.
I see that variant has a space in it, does that work it correctly? My
original idea was that spaces would not be allowed, but didn't realise
to add a check for that.
--
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 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 14:59 QCA4019 hw1.0: Add P&W R619AC specific BDFs gowhdok
2022-01-21 13:56 ` 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=87tudxb3b2.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=gowhdok@mailfence.com \
/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