From: Paul Sajna <sajattack@postmarketos.org>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, phone-devel@vger.kernel.org,
dmitry.baryshkov@oss.qualcomm.com
Subject: ath10k-firmware: WCN3990 hw1.0: sdm845-lg-judyln board file
Date: Fri, 26 Dec 2025 12:56:23 -0800 [thread overview]
Message-ID: <c4ae548c-468d-4451-87dd-460b4e72945d@postmarketos.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
ath10k Firmware for LG G7 ThinQ smartphone (SDM845 SOC)
bdwlan files extracted from android of actual device
md5sum 797c77f75addb87033e4945003727a01
Created from
https://gitlab.com/sajattack/ath10k-firmware/-/tree/add-judyln/lg-judyln
I'm not sure if the ch0 and ch1 files (seen at link above) should also
be included or how
log:
ath10k_snoc 18800000.wifi: qmi chip_id 0x30214 chip_family 0x4001
board_id 0xff soc_id 0x40030001
ath10k_snoc 18800000.wifi: qmi fw_version 0x200880bf fw_build_timestamp
2019-02-17 22:34 fw_build_i
d QC_IMAGE_VERSION_STRING=WLAN.HL.2.0.c4-00191-QCAHLSWMTPLZ-1.190589.1
ath10k_snoc 18800000.wifi: wcn3990 hw1.0 target 0x00000008 chip_id
0x00000000 sub 0000:0000
ath10k_snoc 18800000.wifi: kconfig debug 1 debugfs 1 tracing 0 dfs 0
testmode 0
ath10k_snoc 18800000.wifi: firmware ver api 5 features
wowlan,mgmt-tx-by-reference,non-bmi crc32 b3d4b790
ath10k_snoc 18800000.wifi: htt-ver 3.57 wmi-op 4 htt-op 3 cal file
max-sta 32 raw 0 hwcrypto 1
ath10k_snoc 18800000.wifi: invalid MAC address; choosing random
ath: EEPROM regdomain: 0x819a
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x5e
ath: Country alpha2 being used: KR
ath: Regpair used: 0x5e
[-- Attachment #2: bus=snoc,qmi-board-id=ff,qmi-chip-id=30214,variant=lg_judyln.bin --]
[-- Type: application/octet-stream, Size: 19256 bytes --]
reply other threads:[~2025-12-26 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c4ae548c-468d-4451-87dd-460b4e72945d@postmarketos.org \
--to=sajattack@postmarketos.org \
--cc=ath10k@lists.infradead.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=phone-devel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).