Libertas with if_spi on pxa270

[Uli Luckas]

On Wednesday, 28. January 2009, Mike Rapoport wrote:
> Uli Luckas wrote:
> > On Tuesday, 27. January 2009, Mike Rapoport wrote:
> >> Dan,
> >
> > Does that mean, you got it working on PXA? Mine won't work.
> > On pxa270, kernel 2.6.27.3 + "gspi patch" + "16bit/word spi mode" I get
> > the following log:
> >
> > Jan 26 19:39:44 [kernel] [  242.422220] libertas_spi: Libertas SPI driver
> > Jan 26 19:39:44 [kernel] [  242.425066] firmware: requesting
> > libertas/gspi8686_hlp.bin
> > Jan 26 19:39:45 [kernel] [  243.089646] firmware: requesting
> > libertas/gspi8686.bin
> > Jan 26 19:39:49 [kernel] [  247.049868] libertas: command 0x0003 timed
> > out Jan 26 19:39:49 [kernel] [  247.049937] libertas: requeueing command
> > 0x0003 due to timeout (#1)
> > Jan 26 19:39:49 [kernel] [  247.051820] libertas: Received result 0 to
> > command 3 after 1 retries
> > Jan 26 19:39:49 [kernel] [  247.051989] libertas: 00:15:af:3a:8a:9a, fw
> > 9.70.10p0, cap 0x00000303
> > Jan 26 19:39:49 [kernel] [  247.057863] libertas: Received CMD_RESP with
> > invalid sequence 1 (expected 2)
> > Jan 26 19:39:52 [kernel] [  250.049932] libertas: command 0x0028 timed
> > out Jan 26 19:39:52 [kernel] [  250.050016] libertas: requeueing command
> > 0x0028 due to timeout (#1)
> > Jan 26 19:39:52 [kernel] [  250.051814] libertas: Received result 0 to
> > command 28 after 1 retries
> > Jan 26 19:39:52 [kernel] [  250.053530] libertas: Received CMD_RESP with
> > invalid sequence 2 (expected 3)
> > Jan 26 19:39:55 [kernel] [  253.049850] libertas: command 0x001d timed
> > out Jan 26 19:39:55 [kernel] [  253.049919] libertas: requeueing command
> > 0x001d due to timeout (#1)
> > Jan 26 19:39:55 [kernel] [  253.051795] libertas: Received result 0 to
> > command 1d after 1 retries
> > Jan 26 19:39:55 [kernel] [  253.053982] libertas: Received CMD_RESP with
> > invalid sequence 3 (expected 4)
> > Jan 26 19:39:58 [kernel] [  256.049914] libertas: command 0x00a3 timed
> > out Jan 26 19:39:58 [kernel] [  256.050000] libertas: requeueing command
> > 0x00a3 due to timeout (#1)
> > Jan 26 19:39:58 [kernel] [  256.052128] libertas: Received result 2 to
> > command a3 after 1 retries
> > Jan 26 19:39:58 [kernel] [  256.052278] libertas: PREP_CMD: command
> > 0x00a3 failed: 2
> > Jan 26 19:39:58 [kernel] [  256.054505] libertas: Received CMD_RESP with
> > invalid sequence 4 (expected 5)
> > Jan 26 19:40:01 [kernel] [  259.049833] libertas: command 0x00a3 timed
> > out Jan 26 19:40:01 [kernel] [  259.049901] libertas: requeueing command
> > 0x00a3 due to timeout (#1)
> > Jan 26 19:40:01 [kernel] [  259.052018] libertas: Received result 2 to
> > command a3 after 1 retries
> > Jan 26 19:40:01 [kernel] [  259.052146] libertas: PREP_CMD: command
> > 0x00a3 failed: 2
> > Jan 26 19:40:01 [kernel] [  259.052205] libertas: eth0: Marvell WLAN
> > 802.11 adapter
> >
> > Any idea what could be going wrong here?
>
> From what I can tell, libertas initialization is successful. The failed
> commands are not supported by G-SPI firmware. 
I am using the firmware from the linux-firmware git tree. If this firmware 
does not support some of the commands, then everyone should see these 
messages.

What about the "Received CMD_RESP with invalid sequence n (expected n+1)" 
messages? Is anyone else seeing those? Are they part of my problem? Or do 
they hint at a seperate problem, maybe triggered by the 'real' problem?

> Can you actually use eth0 after the libertas_spi is loaded?
>
'ifconfig eth0 up' works, 'iwlist eth0 scan' does not work. I get many more 
messages like the ones quoted above and after quite a while the scan fails.
I've not tried to assoicate to an AP yet.

thanks,
Uli

-- 

------- ROAD ...the handyPC Company - - -  ) ) )

Uli Luckas
Head of Software Development

ROAD GmbH
Bennigsenstr. 14 | 12159 Berlin | Germany
fon: +49 (30) 230069 - 62 | fax: +49 (30) 230069 - 69
url: www.road.de

Amtsgericht Charlottenburg: HRB 96688 B
Managing director: Hans-Peter Constien