Kalle,
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?
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
Jon
> That's right, AR9374 is basically AR6004 with USB. Don't ask me why :)
Latest ath6kl should support is. I can't remember what kernel version
has the full support, but I'm pretty sure 3.3 didn't support it yet. But
I should update ath6kl documentation to mention this, thanks for
pointing this out.
> Kalle
Would it be possible to get hw1.3 pushed up to linux-firmware git?
Jon
Add support for AR6004 hardware with version 1.3 and has
id 0x31c8088a.
Signed-off-by: Bala Shanmugam <[email protected]>
---
drivers/net/wireless/ath/ath6kl/core.h | 7 +++++++
drivers/net/wireless/ath/ath6kl/init.c | 20 ++++++++++++++++++++
drivers/net/wireless/ath/ath6kl/sdio.c | 3 +++
drivers/net/wireless/ath/ath6kl/usb.c | 3 +++
4 files changed, 33 insertions(+)
diff --git a/drivers/net/wireless/ath/ath6kl/core.h
b/drivers/net/wireless/ath/ath6kl/core.h
index c655438..2d1b8ac 100644
--- a/drivers/net/wireless/ath/ath6kl/core.h
+++ b/drivers/net/wireless/ath/ath6kl/core.h
@@ -192,6 +192,13 @@ enum ath6kl_hw_flags {
#define AR6004_HW_1_2_DEFAULT_BOARD_DATA_FILE \
AR6004_HW_1_2_FW_DIR "/bdata.bin"
+/* AR6004 1.3 definitions */
+#define AR6004_HW_1_3_VERSION 0x31c8088a
+#define AR6004_HW_1_3_FW_DIR "ath6k/AR6004/hw1.3"
+#define AR6004_HW_1_3_FIRMWARE_FILE "fw.ram.bin"
+#define AR6004_HW_1_3_BOARD_DATA_FILE "ath6k/AR6004/hw1.3/bdata.bin"
+#define AR6004_HW_1_3_DEFAULT_BOARD_DATA_FILE "ath6k/AR6004/hw1.3/bdata.bin"
>> 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?
Hi Kalle,
We have two units, both come up as 0x31c8088a using your kernel on x86
Ubuntu or using a recent compat-wireless on our arm platform. The PN on
the chip is
AR9374X-4L3E which is on a usb board
The bubble wrap has the following....
UB134-055
QCABUB134
HT0430121
Jon
Kalle,
Gave the firmware a try using your ath6kl-next branch (pulled yesterday).
I can connect and move data to open networks only. WPA connections appear
to keep trying to associate over and over at these states....
ASSOCIATED -> 4WAY_HANDSHAKE
4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
wpa_supplicant log attached. I tried a couple of routers / APs.
Jon
> Hi Jon,
>
> On 07/17/2012 07:40 PM, Kalle Valo wrote:
>> On 07/17/2012 05:53 PM, [email protected] wrote:
>>> Would it be possible to get hw1.3 pushed up to linux-firmware git?
>>
>> We are working on it. Hopefully we can push it soon.
>
> Here's the firmware file and board data we are planning to send to
> linux-firmware.git soon. Please let me know if you have any problems
> with them.
>
> Kalle
>
On 07/10/2012 04:42 PM, [email protected] wrote:
> We have two units, both come up as 0x31c8088a using your kernel on x86
> Ubuntu or using a recent compat-wireless on our arm platform. The PN on
> the chip is
>
> AR9374X-4L3E which is on a usb board
>
> The bubble wrap has the following....
> UB134-055
> QCABUB134
> HT0430121
Ok, I got more info inside QCA now. 0x31c8088a is a valid hw id for
ar6004/ar9374, it's just that nobody added the support to ath6kl. We are
working on adding it to ath6kl. I cannot give any schedule, but I hope
it happens soon.
Kalle
+ath6kl-devel
Hi Jon,
On 06/28/2012 12:28 AM, [email protected] 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
On 07/17/2012 05:53 PM, [email protected] wrote:
> Would it be possible to get hw1.3 pushed up to linux-firmware git?
We are working on it. Hopefully we can push it soon.
Kalle
Hi Jon,
On 07/17/2012 07:40 PM, Kalle Valo wrote:
> On 07/17/2012 05:53 PM, [email protected] wrote:
>> Would it be possible to get hw1.3 pushed up to linux-firmware git?
>
> We are working on it. Hopefully we can push it soon.
Here's the firmware file and board data we are planning to send to
linux-firmware.git soon. Please let me know if you have any problems
with them.
Kalle
Hi Jon,
sorry for the late answer, I was again on vacation.
On 07/20/2012 11:09 PM, [email protected] wrote:
> Kalle,
>
> Gave the firmware a try using your ath6kl-next branch (pulled yesterday).
> I can connect and move data to open networks only. WPA connections appear
> to keep trying to associate over and over at these states....
>
> ASSOCIATED -> 4WAY_HANDSHAKE
> 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
>
> wpa_supplicant log attached. I tried a couple of routers / APs.
There's a developer working on this issue. I don't know when he will
send the fix but let's hope that it will happen soon.
Thanks for the report, keep them coming.
Kalle
On 08/17/2012 03:03 PM, Jonathan Bagg wrote:
> Also, I was only able to get a max of 65Mbps / MCS7. I think the 9374
> is capable of faster? I've never used a 2-stream device....not sure if I
> need to configure it to use the 2-streams, or if the ath6kl driver only
> supports up to MCS7?
I don't actually know. I need to find out from the team who added ar6004
support to ath6kl and I will get back to you (or preferably someone from
that team will).
Kalle
> Hi Jon,
>
> sorry for the late answer, I was again on vacation.
No worries.
Also, I was only able to get a max of 65Mbps / MCS7. I think the 9374
is capable of faster? I've never used a 2-stream device....not sure if I
need to configure it to use the 2-streams, or if the ath6kl driver only
supports up to MCS7?
Jon