ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A42 specific BDFs
Date: Fri, 21 Jan 2022 15:13:52 +0200	[thread overview]
Message-ID: <87tudxfcz3.fsf@kernel.org> (raw)
In-Reply-To: <3587857.nm731UhE9D@bentobox> (Sven Eckelmann's message of "Mon,  01 Jul 2019 11:43:06 +0200")

Sven Eckelmann <sven@narfation.org> writes:

> [resent of mail from 2019-06-11; seems like @datto.com mail server ate the
>  outgoing mails]
>
> Hi,
>
> The OpenMesh AA2 AP requires two special BDFs to get the Wi-Fi PHYs working 
> (correctly). The  bmi-board-id='s would clash with one of the the IPQ401X 
> AP-DK boards because QCA doesn't provide special IDs for customers and seems 
> to use the AP-DK board-ids in the wifi firmware to change its behavior. 
>
> This update contains:
>
> * add of the antenna gain
> * CTLs for DFS channels
>
> It supersedes https://lkml.kernel.org/r/2339663.SsakJrGtyZ@bentobox
>
>
> Now to the questions from the wiki page [1]:
>
> * description for what hardware this is:
>
>   - it is a QCA4019 based module (based on qcom-ipq4019-ap.dk01.1)
>   - 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)
>
>   - it was created by the ODM and QCA for the OpenMesh A42
>   - was provided by the ODM to OpenMesh for this product (this includes
>     distribution)
>   - it is the latest release from 2018-11-28 (with fix to have
>     antennagain at correct position)
>
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
>
>   - QCA4019 hw1.0
>
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=OM-A42
>       md5sum: 3556213619f465b53348836ff7444f01
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=OM-A42
>       md5sum: f836ec38fe8b5c169a2a33a9fd9afae7
>
> * 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 QCA4019/hw1.0/board-2.bin:

New:


Changed:
bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=OM-A42
bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=OM-A42

Deleted:

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

https://github.com/kvalo/ath10k-firmware/commit/bc425879a4f43bd2b0c2c56298fc88ebeb711af0

-- 
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

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01  9:43 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A42 specific BDFs Sven Eckelmann
2022-01-21 13:13 ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-10 13:17 Sven Eckelmann
2019-06-28 13:40 ` Kalle Valo

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=87tudxfcz3.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=sven@narfation.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