MuRata WiFi Module with Marvell 88w8686

[Anthony Ginger]

Yes, my fw doesn't support mesh. Will it cause trouble if I use this driver?

After I upgrade to the driver from wireless-testing, I got:
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas: 00:13:e0:ab:e3:03, fw 9.70.3p6, cap 0x00000303
libertas: unidentified region code; using the default (USA)
libertas: PREP_CMD: command 0x00a3 failed: 2
libertas: PREP_CMD: command 0x00a3 failed: 2
libertas: eth1: Marvell WLAN 802.11 adapter

And the performance seems a little better.
# ./arm-linux-iperf -c 10.0.0.110 -i 10 -w 1M
------------------------------------------------------------
Client connecting to 10.0.0.110, TCP port 5001
TCP window size:  208 KByte (WARNING: requested 1.00 MByte)
------------------------------------------------------------
[  5] local 10.0.0.2 port 52743 connected with 10.0.0.110 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec  17.1 MBytes  14.4 Mbits/sec

Thanks!
Tony


2008/6/18 Holger Schurig <hs4233 at mail.mn-solutions.de>:
>> libertas: PREP_CMD: command 0x0022 failed: 2
>
> That's CMD_802_11_DATA_RATE. A command that newer firmwares don't
> understand and a command that isn't even needed at all for older
> firmwares. It looks like you don't use the current libertas
> driver from wireless-testing, because I removed that command.
>
>> libertas: PREP_CMD: command 0x00a3 failed: 2
>> libertas: PREP_CMD: command 0x00a3 failed: 2
>
> That's CMD_MESH_CONFIG. Seems your firmware doesn't support mesh.
>
>> And if I use enable SDIO interrupts, I will get "libertas:
>> Command 3 timed out" # mmc0: new SDIO card at address 0001
>> libertas: Command 3 timed out
>
> Hmm, not sure if this is command sequence no 3 or command 3. My
> commits always emit commands in the printf-style 0x%04x :-)
>
> If it is command 0x0003, then it would be CMD_GET_HW_SPEC and
> that your driver works without CMD_GET_HW_SPEC would be by
> chance. AFAIK the driver get's its MAC-address out of the card
> via CMD_GET_HW_SPEC ...   so what does "ifconfig" report for
> you?
>
>
> I cannot say more about this unless you enable LBS_DEB_CMD and
> LBS_DEB_HEX, maybe even LBS_DEB_HOST (don't send my sdio debug
> things, I cannot decipher them and don't really care).
>