Scan problem (CRC) (was: Difference betwwen linux 2.6.24 and 2.6.25 ?)

[Holger Schurig]

> I have added libertas_debug=0x7fffff when insmod:ing libertas
> and attached is the debug including all commands after the
> first GET_HW_SPEC (including some debug from our sdio driver)

Ugh. I didn't ask for that much :-/



> My command looks ok, I think, but I do not get any response.
> Instead a INT_DATA_CRC error interrupt:

So you found your problem. I'm quite certain this is not an
libertas issue, but a data transfer problem to/from your device.

Libertas doesn't use CRCs for normal commands (it uses it only
for downloading firmware).

So the following are just things that I noticed, and they might be
quite unrelated to the problem.



> libertas: DATA_RATE: fake current rate 0x6c

I haven't seen a patch for this and cannot judge if that is a
problem or not.

When your driver executes CMD_802_11_RF_CHANNEL, it sends this to
the card:

> libertas DNLD_CMD: 1d 00 30 00 04 00 00 00 00 00 05 bf 00 00 e7 c0
> libertas DNLD_CMD: 28 02 e7 c0 e0 9e 05 bf 00 00 00 00 14 3d dd c0
> libertas DNLD_CMD: 08 3d dd c0 74 5d 03 c0 80 5a 03 c0 44 3d dd c0

the driver that is rigth now in wireless-testing doesn't send this
junk anymore:

libertas DNLD_CMD: 1d 00 30 00 04 00 00 00 00 00 00 00 00 00 00 00
libertas DNLD_CMD: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
libertas DNLD_CMD: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

> libertas: PREP_CMD: command 0x00a3 failed: 2

This is expected, your firmware doesn't support mesh, it seems.

> libertas DNLD_CMD: 4d 00 10 00 07 00 00 00 01 00 00 40 8c 18 34 55

Maybe because you're using the "ip" command (I'm using "ifconfig")
does the driver download a MAC address into the card. That doesn't
happen on my side.

Why this happens twice remains a secret I don't have insight into ...



> sdhci [sdhci_prepare_data()]: tsac 1000 ms nsac 0 clk

What does this mean?  Note that some commands, e.g. the scan
command, can take long (not one second, but hey, it takes time).
Does something in your sdhci driver need a reply within a
specific timeframe?


If you don't run "iwlist eth1 scan", but "iwconfig eth1", do you
get some sensible output?  Or do you also get weird errors?