From: Dylan Van Assche <me@dylanvanassche.be>
To: ath10k@lists.infradead.org, linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: ath10k-firmware: WCN3990: Add board file for SHIFTPHONES SHIFT6mq
Date: Fri, 25 Aug 2023 17:16:14 +0200 [thread overview]
Message-ID: <55665952-c6ce-d097-d4b7-4cacd324eb06@dylanvanassche.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Hello Kalle,
I would like to include the board file for the SHIFTPHONES SHIFT6mq
smartphone.
This smartphone is manufactured by SHIFTPHONES and uses the Snapdragon
SDM845 SoC.
At postmarketOS, we run the mainline kernel on this phone so shipping
this board file
from upstream would be a great addition. Below, the questions from the wiki:
* description for what hardware this is:
Smartphone with a SDM845 chip and a WCN3990 Bluetooth/WiFi chip.
The WCN3990 chip is connected to 2 QM488xx radios, one is used
for 2.4Ghz and the other one for 5Ghz radio.
* origin of the board file (did you create it yourself or where you
downloaded)
Extracted from the stock firmware.
* ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
- WCN3990 hw1.0
+ bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=shift_axolotl
sha256sum:
082f65dad7b2ee938911d60a0f4f9ef8df18417ce69e9f42c9e947e961d18f30
md5sum: 5dce0c544a7a8036ebd4beaeba3d244b
* 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")
Kind regards,
Dylan Van Assche
[-- Attachment #2: bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=shift_axolotl.bin --]
[-- Type: application/octet-stream, Size: 19152 bytes --]
next reply other threads:[~2023-08-25 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 15:16 Dylan Van Assche [this message]
2023-12-07 14:56 ` ath10k-firmware: WCN3990: Add board file for SHIFTPHONES SHIFT6mq 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=55665952-c6ce-d097-d4b7-4cacd324eb06@dylanvanassche.be \
--to=me@dylanvanassche.be \
--cc=ath10k@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).