From: Kalle Valo <kvalo@qca.qualcomm.com>
To: 孙建希 <ycsunjane@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k otp.bin board.bin firmware.bin art.bin?
Date: Wed, 19 Apr 2017 11:37:03 +0000 [thread overview]
Message-ID: <87zifc8w80.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CABWe71yxXG5VMaPPUK3HeYjNDOn7PiHk1AJy8WnXb-nntOMz4g@mail.gmail.com> ("孙建希"'s message of "Wed, 19 Apr 2017 11:32:19 +0800")
孙建希 <ycsunjane@gmail.com> writes:
> I am debugging ath10k QCA986x 5g WNIC. And installed the firmware. But
> the card did not rise.
Did you also install the board.bin?
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/ath10k/QCA988X/hw2.0/board.bin
> The kernel log is as follows:
>
> [ 9.320705] ath10k_pci 0000:00:00.0: firmware ver 10.2.4-1.0-00029
> api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 88595bb8
> [ 9.365636] ath10k_pci 0000:00:00.0: board id is not exist in otp, ignore it
> [ 9.372894] ath10k_pci 0000:00:00.0: Direct firmware load for
> ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Full log would be much better, you might miss something important.
> What is the board id in otp?
It's used to identify different board versions but not all boards
support that. You can ignore that error message. Actually in commit
7be52c03bbf7 we downgraded that error message to a debug message.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-04-19 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 3:32 ath10k otp.bin board.bin firmware.bin art.bin? 孙建希
2017-04-19 11:37 ` Kalle Valo [this message]
2017-04-19 14:58 ` 孙建希
2017-04-20 6:27 ` Kalle Valo
2017-04-20 7:10 ` 孙建希
2017-04-20 7:31 ` 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=87zifc8w80.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=ycsunjane@gmail.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 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.