From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Please update board-2.bin for QCA9888
Date: Thu, 9 Mar 2017 12:30:47 +0000 [thread overview]
Message-ID: <87o9xa4oqb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <58C14C2D.902@candelatech.com> (Ben Greear's message of "Thu, 9 Mar 2017 04:35:57 -0800")
Ben Greear <greearb@candelatech.com> writes:
> On 03/08/2017 11:21 PM, Valo, Kalle wrote:
>> Ben Greear <greearb@candelatech.com> writes:
>>
>>> Newer 9886 (which use the 9888 firmware it seems) NICs will not
>>> boot unless you use the board-2.bin from the codeaura repo.
>>>
>>> Kalle: Could you update your repo to the latest from codeaura so that it is
>>> easy to pull the latest board file into LEDE?
>>>
>>> If you have reason not to, please let me know.
>>
>> I'm not involved with codeaurora repositories so I don't know what file
>> you are talking about. What's the URL?
>>
>
> git://codeaurora.org/quic/qsdk/oss/firmware/ath10k-firmware
>
> [greearb@ben-dt3 ath10k-firmware]$ ls -l ath10k/QCA9888/hw2.0/board-2.bin
> -rw-rw-r--. 1 greearb greearb 60660 Mar 2 16:20 ath10k/QCA9888/hw2.0/board-2.bin
>
> [greearb@ben-dt3 ath10k-firmware]$ md5sum ath10k/QCA9888/hw2.0/board-2.bin
> 4fffcdf246cea4a4fd5ba67730262563 ath10k/QCA9888/hw2.0/board-2.bin
>
> I actually tested an older version of that file, but I assume the more
> recent one works
> fine too. I don't have a 9886/8 system available for testing at the moment.
Ok, thanks. I'll ask internally why nobody has submitted that to me.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-03-09 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 0:25 Please update board-2.bin for QCA9888 Ben Greear
2017-03-09 7:21 ` Valo, Kalle
2017-03-09 12:35 ` Ben Greear
2017-03-09 12:30 ` Valo, Kalle [this message]
2017-03-09 17:52 ` Adrian Chadd
2017-04-20 11:18 ` 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=87o9xa4oqb.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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