From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org
Subject: Re: README for the ath10k firmware repository?
Date: Mon, 28 Oct 2013 09:51:00 -0700 [thread overview]
Message-ID: <526E95F4.1010904@candelatech.com> (raw)
In-Reply-To: <87a9htephy.fsf@kamboji.qca.qualcomm.com>
On 10/28/2013 02:03 AM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> I noticed some new firmware images were added to the ath10k firmware
>> repository ( https://github.com/kvalo/ath10k-firmware.git).
>>
>> Could someone that knows add a small README that describes what firmware
>> does what?
>
> I added a small readme and wrote a bit more information to the wiki:
>
> https://github.com/kvalo/ath10k-firmware
> http://wireless.kernel.org/en/users/Drivers/ath10k/firmware
>
> Do those help?
>
>> For instance, I was thinking that maybe I should rename firmware-2.bin
>> to firmware.bin on the host machine in order to use it..but that makes
>> my system not boot.
>
> You should not rename the files, except firmware-2.bin-10.1.389 ->
> firmware-2.bin.
Yes, that does help.
It is correct to say that if firmware-2.bin exists then the
firmware.bin and otp.bin will always be ignored for recent
ath10k drivers?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-10-28 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 22:07 README for the ath10k firmware repository? Ben Greear
2013-10-28 9:03 ` Kalle Valo
2013-10-28 16:51 ` Ben Greear [this message]
2013-10-28 16:54 ` 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=526E95F4.1010904@candelatech.com \
--to=greearb@candelatech.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