From: Sven Eckelmann <sven@narfation.org>
To: ath10k@lists.infradead.org
Subject: ath10k-firmware: QCA4019 hw1.0: Update Plasma Cloud PA1200 specific BDFs
Date: Sat, 22 Jan 2022 09:36:12 +0100 [thread overview]
Message-ID: <2931430.FNKZsP7sFK@sven-l14> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1708 bytes --]
Hi,
the firmware 10.4-3.6-00140 crashed [1] when the 5GHz of the PA1200 was
set up. It was noticed that this is somehow related to the option
baseEepHeader.nonLinearTxFir which was set to 1. There was no feedback from
QCA and the manufacturer about this problem. So as only known workaround (with
the latest firmware), this option was set to 0 and the modified BDFs were
integrated in OpenWrt [2].
Now to the questions from the wiki page [3]:
* description for what hardware this is:
- it is a IPQ4019 based board
- one QCA40xx radio is used as 2.4GHz radio
- one QCA40xx radio is used as 5GHz radio
* origin of the board file (did you create it yourself or where you
downloaded)
- the file from ath10k-firmware was modified by setting the
baseEepHeader.nonLinearTxFir to 0 to work around a crash in the ath10k-
firmware
* ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
- BoardNames[0]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=PlasmaCloud-PA1200'
BoardLength[0]: 12064
BoardCRC32[0]: b587e755
BoardMD5[0]: 4129d301ee1a697af1fa311afcad6f87
- BoardNames[1]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=PlasmaCloud-PA1200'
BoardLength[1]: 12064
BoardCRC32[1]: 680fe0ec
BoardMD5[1]: 928c27310acfdef356ce6d6a5cdfc1f2
* 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,
Sven
[1] https://lore.kernel.org/ath10k/3423718.UToCqzeSYe@ripper/
[2] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8b090708208501a60e71d0118b9860dd401d7d8d
[3] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
[-- Attachment #1.1.2: bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=PlasmaCloud-PA1200.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]
[-- Attachment #1.1.3: bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=PlasmaCloud-PA1200.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2022-01-22 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 8:36 Sven Eckelmann [this message]
2022-04-13 9:04 ` ath10k-firmware: QCA4019 hw1.0: Update Plasma Cloud PA1200 specific BDFs 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=2931430.FNKZsP7sFK@sven-l14 \
--to=sven@narfation.org \
--cc=ath10k@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.