archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <>
To: "Peter Adkins" <>
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add Linksys WHW01 v1 specific BDFs
Date: Fri, 21 Jan 2022 15:53:27 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Peter Adkins's message of "Mon, 21 Dec 2020 18:46:03 +0000")

"Peter Adkins" <> writes:

> In order to properly add support to OpenWrt for the Linksys WHW01 v1 (FCC ID Q87-0333) [1], BDFs were required to be extracted from the vendor's firmware (version [2]). Without these the radios did not appear to operate correctly; the 5GHz radio was unable to scan, and when running in AP mode, clients were unable to connect.
> The vendor firmware appears to provide a number of board files which are installed at device power-on depending on the configured region - AU, FCC, EU, etc. Only the FCC board files have been included here, as I'm unsure whether all files should be submitted and whether there are any differences (although their md5s did not match)?
> Information requested, per the wiki page [3]:
> * description for what hardware this is:
>   - it is a IPQ4018 based board
>     - one qca4019 radio is used as 2.4GHz radio
>     - one qca4019 radio is used as 5GHz radio
> * origin of the board file (did you create it yourself or where you downloaded)
>   - Extracted from Linksys WHW01 v1 firmware ( [2]
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
>   - bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=linksys-whw01-v1
>     md5: 92f5a223a963211d884b6211385dfa91
>   - bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=linksys-whw01-v1
>     md5: 5bb0357df9cf3614fe4d9db696d09e43

Thanks, added to QCA4019/hw1.0/board-2.bin:




2 board image(s) added, 0 changed, 0 deleted, 86 in total


ath10k mailing list

      reply	other threads:[~2022-01-21 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 18:46 ath10k-firmware: QCA4019 hw1.0: Add Linksys WHW01 v1 specific BDFs Peter Adkins
2022-01-21 13:53 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).