From: Kalle Valo <kvalo@kernel.org>
To: Joshua Roys <roysjosh@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA9984 hw1.0: Add ASUS RT-AC42U specific BDFs
Date: Fri, 21 Jan 2022 17:12:05 +0200 [thread overview]
Message-ID: <87pmol86nu.fsf@kernel.org> (raw)
In-Reply-To: <CANoNxL_-ixM9Am2O30OUrNFux9zO_YUMPjh37e6PR9hZEyEYFQ@mail.gmail.com> (Joshua Roys's message of "Mon, 10 Jan 2022 10:53:13 -0500")
Joshua Roys <roysjosh@gmail.com> writes:
> This is in support of the OpenWRT bringup for the ASUS RT-ACRH17 a/k/a
> RT-AC42U (online) a/k/a RT-AC82U (GPL sources).
>
> * description of hardware
> - QCA4019-based board, the vendor sources build off of DK04.1
> - QCA4019 is used as 2.4 GHz radio (BDF in previous email)
> - QCA9984 is used as 5 GHz radio
>
> * origin of the board file
> - Pulled from the firmware image 3.0.0.4-382-52517-gb4d36a6
> - Identical to board file in GPL sources
>
> * IDs to be used with the board file
> - bus=pci,bmi-chip-id=0,bmi-board-id=3,variant=ASUS-RT-AC42U
>
> * md5sum/sha256sum of the board file
> - MD5 d6add1386d2353d08f8a0d86f243a5c1
> - SHA256 e6e076ab66b0e8eff9f78e120659258c537fd9d9b558142d5e14575cda854534
>
> Board file is attached.
Thanks, added to QCA9984/hw1.0/board-2.bin:
New:
bus=pci,bmi-chip-id=0,bmi-board-id=3,variant=ASUS-RT-AC42U
Changed:
Deleted:
1 board image(s) added, 0 changed, 0 deleted, 20 in total
https://github.com/kvalo/ath10k-firmware/commit/069b752fd26245aff0a00344bf8fc469bfa65d17
--
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 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 15:53 ath10k-firmware: QCA9984 hw1.0: Add ASUS RT-AC42U specific BDFs Joshua Roys
2022-01-21 15:12 ` 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=87pmol86nu.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=roysjosh@gmail.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 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.