From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <drwho@infidigm.net>
Cc: Julian Calaby <julian.calaby@gmail.com>,
Sujith Manoharan <c_manoha@qca.qualcomm.com>,
Mohammed Shafi <shafi.wireless@gmail.com>,
<linux-wireless@vger.kernel.org>,
ath6kl-devel <ath6kl-devel@qualcomm.com>
Subject: Re: ar6004 / ar9374 firmware
Date: Tue, 10 Jul 2012 13:49:41 +0300 [thread overview]
Message-ID: <4FFC08C5.2050606@qca.qualcomm.com> (raw)
In-Reply-To: <43a66e0f20b45e9cc461272e83f2c4e4.squirrel@www.infidigm.net>
+ath6kl-devel
Hi Jon,
On 06/28/2012 12:28 AM, drwho@infidigm.net wrote:
> I've noticed in core.h in the ath6kl driver that it is defining the
> following firmware for the ar6004....
>
> ath6k/AR6004/hw1.0/fw.ram.bin
> ath6k/AR6004/hw1.1/fw.ram.bin
> ath6k/AR6004/hw1.2/fw.ram.bin
>
> In linux-firmware.git all that exists is...
>
> ath6k/AR6004/hw1.2/fw-2.bin
> ath6k/AR6004/hw1.2/bdata.bin
>
> fw-2.bin need a rename?
fw.ram.bin is for FW API 1 and fw-2.bin is FW API 2. So fw-2.bin is
correct, I'll send a patch for ath6kl to fix this.
> Also, my UB134 is coming up with a device ID of 0x31c8088a?
>
> [ 361.676440] ath6kl: Unsupported hardware version: 0x31c8088a
> [ 361.680437] ath6kl: Failed to init ath6kl core: -22
> [ 361.680491] ath6kl_usb: probe of 2-1:1.0 failed with error -22
> [ 361.680520] usbcore: registered new interface driver ath6kl_usb
That's odd, I'm not familiar with 0x31c8088a. I wonder if it's corrupted
somehow or is it a valid device id? Does anyone from ath6kl-devel know?
Kalle
next prev parent reply other threads:[~2012-07-10 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 21:28 ar6004 / ar9374 firmware drwho
2012-07-10 10:49 ` Kalle Valo [this message]
2012-07-10 13:42 ` ar6004 / ar9374 drwho
2012-07-11 12:48 ` Kalle Valo
2012-07-17 14:53 ` ath6kl: Add support for AR6004 hardware version 1.3 drwho
2012-07-17 16:40 ` Kalle Valo
2012-07-19 9:36 ` Kalle Valo
2012-07-20 20:09 ` drwho
2012-08-17 7:35 ` Kalle Valo
2012-08-17 12:03 ` Jonathan Bagg
2012-08-17 14:03 ` 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=4FFC08C5.2050606@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=c_manoha@qca.qualcomm.com \
--cc=drwho@infidigm.net \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).