ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Robert Marko <robimarko@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Update 8devices Habanero specific BDFs
Date: Fri, 21 Jan 2022 15:46:16 +0200	[thread overview]
Message-ID: <87wnitcic7.fsf@kernel.org> (raw)
In-Reply-To: <CAOX2RU4r338J_iAbK50OFQbuWP1_KgMfCGm2s0So2P+2P=gwkg@mail.gmail.com> (Robert Marko's message of "Fri, 21 Jan 2022 14:34:13 +0100")

Robert Marko <robimarko@gmail.com> writes:

> On Fri, 21 Jan 2022 at 14:25, Kalle Valo <kvalo@kernel.org> wrote:
>>
>> Robert Marko <robimarko@gmail.com> writes:
>>
>> > I am currently working on the 8devices Habanero support for
>> > OpenWrt. This
>> > 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 improves 5GHz radio.
>> >
>> > Now to the questions from the wiki page [1]:
>> >
>> > * description for what hardware this is:
>> >
>> >   - it is a QCA4019 based module
>> >   - 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 pulled from the 8devices OpenWrt fork
>> >   - it is based on latest version
>> >
>> > * 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=8devices-Habanero
>> >      md5sum:
>> >      64d0817da715875483d323f2bb0c898c
>> >
>> >   + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=8devices-Habanero
>> >      md5sum:
>> >      56202ea33e96f16c65b75d464451c251
>> >
>> > * 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")
>>
>> Do note that it seems that only one board file contents was actually
>> changed, was that on purpose?
>
> Yes, only the 5GHz radio had an update.

Good, thanks for checking.

> 8devices released new BDF-s last year that fix the thermal readings.
>
> Do you mind if I send the updated ones upstream?

Sure, why not? My board file queue is just really long but I'm going
through it at the moment.

-- 
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:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23  9:43 ath10k-firmware: QCA4019 hw1.0: Update 8devices Habanero specific BDFs Robert Marko
2022-01-21 13:25 ` Kalle Valo
2022-01-21 13:34   ` Robert Marko
2022-01-21 13:46     ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-08 12:38 Mantas
2023-03-17 11:45 ` 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=87wnitcic7.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=robimarko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox