From: Christian Lamparter <chunkeey@googlemail.com>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Subject: IPQ4019 Firmware: board-2.bin vs board.bin
Date: Fri, 18 Nov 2016 17:46:14 +0100 [thread overview]
Message-ID: <3020314.NNveBmB38o@debian64> (raw)
Hello,
I've acquired a IPQ4019 Router (Asus RT-AC58U). And It has a IPQ4019-SoC.
I'm currently in the process of porting it to LEDE. I can report that the
router is booting and I got the ath10k to work with 4.8.8 +
LEDE's compat-wireless (2016-10-08-1).
Now, I ran across a small discrepancy with the provided firmware for
the IPQ4019. From the ath10k's driver prospective it seems that the
board-2.bin provided on github[0] has the wrong filename:
ath10k_ahb a000000.wifi: Direct firmware load for ath10k/pre-cal-ahb-a000000.wifi.bin failed with error -2
ath10k_ahb a000000.wifi: Falling back to user helper
firmware ath10k!pre-cal-ahb-a000000.wifi.bin: firmware_loading_store: map pages failed
ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
ath10k_ahb a000000.wifi: firmware ver 10.4-3.2.1-00044 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param crc32 b9833652
ath10k_ahb a000000.wifi: failed to fetch board data for bus=ahb,vendor=0000,device=0000,subsystem-vendor=0000,subsystem-devn
ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/board.bin failed with error -2
ath10k_ahb a000000.wifi: Falling back to user helper
firmware ath10k!QCA4019!hw1.0!board.bin: firmware_loading_store: map pages failed
ath10k_ahb a000000.wifi: failed to fetch board data
ath10k_ahb a000000.wifi: failed to fetch board file: -11
ath10k_ahb a000000.wifi: could not probe fw (-11)
Now, If I rename board-2.bin to board.bin it works fine and the device initializes
successfully (and seems to work too):
ath10k_ahb a000000.wifi: Direct firmware load for ath10k/pre-cal-ahb-a000000.wifi.bin failed with error -2
ath10k_ahb a000000.wifi: Falling back to user helper
firmware ath10k!pre-cal-ahb-a000000.wifi.bin: firmware_loading_store: map pages failed
ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
ath10k_ahb a000000.wifi: firmware ver 10.4-3.2.1-00044 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param crc32 b9833652
ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/board-2.bin failed with error -2
ath10k_ahb a000000.wifi: Falling back to user helper
firmware ath10k!QCA4019!hw1.0!board-2.bin: firmware_loading_store: map pages failed
ath10k_ahb a000000.wifi: board_file api 1 bmi_id N/A crc32 9e6ce62c
ath10k_ahb a000000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
What's up with the board-2.bin name? Kalle, can you rename it or
should ath10k look for board-2.bin instead?
Regards,
Christian
[0] <https://github.com/kvalo/ath10k-firmware/tree/master/QCA4019/hw1.0>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2016-11-18 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 16:46 Christian Lamparter [this message]
2016-11-18 17:25 ` IPQ4019 Firmware: board-2.bin vs board.bin Michal Kazior
2016-11-18 18:40 ` Christian Lamparter
2016-11-18 18:45 ` Ben Greear
2016-11-18 19:12 ` Michal Kazior
2016-11-18 21:40 ` Christian Lamparter
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=3020314.NNveBmB38o@debian64 \
--to=chunkeey@googlemail.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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