ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: WCN3990: Add firmware file for the Qualcomm Robotics RB3 / Dragonboard 845c
Date: Wed, 13 Apr 2022 12:12:30 +0300	[thread overview]
Message-ID: <877d7tl535.fsf@kernel.org> (raw)
In-Reply-To: <CAA8EJpphUrxr5gtW0=-tZh-DrKXmHkfFxWMvYRpTUGuCesGCbw@mail.gmail.com> (Dmitry Baryshkov's message of "Sun, 3 Apr 2022 15:04:01 +0300")

Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:

> Hi,
>
> We'd like to ask for inclusion of the board file for the Qualcomm
> Robotics RB3 Platform also known as Thunderomm Dragonboard 845c. It is
> a development platform based on the Qualcomm SDM845 SoC.
> Following the questions from the ath10k wiki page:
>
> * description for what hardware this is
> - It is an SDM845-based platform
> - It uses wcn3990 chip as a WiFi and BT radio
>
> * origin of the board file
>   - It comes from the BSP package distributed by Linaro
> (http://releases.linaro.org/96boards/dragonboard845c/qualcomm/firmware/RB3_firmware_20190529180356-v4.zip)
>
> * ids to be used with the board file
> bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=Thundercomm_DB845C
> bus=snoc,qmi-board-id=ff,qmi-chip-id=30214
> bus=snoc,qmi-board-id=ff
>
> Note, the board comes with the board_id not changed from 0xff.
> Following the example of Chromebook boards we are adding the
> calibration variant to the DT [1].
> I'm asking to include both bdf files: with the variant part and
> without it (for the sake of backwards compatibility).
> However once the patch [1] is accepted it should be fine from my point
> of view if you decide to include just the with-variant patch into the
> public/distributed board database.
>
> * md5sum of each new board file to add
>
> $ md5sum *
> d8dc08c33402920792928c65262b4955  bus=snoc,qmi-board-id=ff,qmi-chip-id=30214.bin
> d8dc08c33402920792928c65262b4955
> bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=Thundercomm_DB845C.bin
>
> $ sha256sum *
> 9bdf7859d8d6a6f41f6b55338b51723335bc9cc24a4d2e20ebaef234859d6fb3
> bus=snoc,qmi-board-id=ff,qmi-chip-id=30214.bin
> 9bdf7859d8d6a6f41f6b55338b51723335bc9cc24a4d2e20ebaef234859d6fb3
> bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=Thundercomm_DB845C.bin

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

New:
bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=Thundercomm_DB845C
bus=snoc,qmi-board-id=ff,qmi-chip-id=30214

Changed:


Deleted:

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

https://github.com/kvalo/ath10k-firmware/commit/22218c422164d618aec37200eae36d85cde3f11e

-- 
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-04-13  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 12:04 ath10k-firmware: WCN3990: Add firmware file for the Qualcomm Robotics RB3 / Dragonboard 845c Dmitry Baryshkov
2022-04-13  9: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=877d7tl535.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=dmitry.baryshkov@linaro.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