Re: [Bluez-users] Once again: Socket CF card and Kernel 2.6

Marcel Holtmann
2005-03-01T08:29:36Z

Hi Mathias,

> > what kind of 2.6 kernel is this? Give 2.6.11-rc5 a chance. Do you see
> > anything special with dmesg?
>
> Before I have tried 2.6.9-1-686 (Debian unstable) and 2.6.10 (from
> www.kernel.org). Now I patched the 2.6.10 up to 2.6.11-rc5, but it seems
> to behave the same - same messages in dmesg as before, still timeout
> when running hciattach (nothing in dmesg after this command)...
> Also the same with the -mh4 patch (against a clean 2.6.10).
>
> I checked what the working 2.4.29 shows in dmesg, maybe this helps
> somewhat:
>
> Inserting the card:
> -----
> cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff
> 0xd8000-0xfffff
> ttyS01 at port 0x02f8 (irq = 11) is a 16C950/954
> -----
>
> modprobe hci_uart:
> -----
> BlueZ HCI UART driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
> Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
> -----
>
> hciattach ttyS1 socket:
> -----
> bcsp_recv: Out-of-order packet arrived, got 1 expected 0
> -----
> (but the bluetooth device works despite this error)
>
> One idea: is there an (easy) way to log what's going on on the ttyS1
> device (I mean the communication between the hci_uart driver and the cf
> card)? This way one could compare the logs of kernel 2.4 and 2.6 and
> maybe see what's wrong...

I am not an serial card expert. This is a problem in the serial
subsystem and a BlueZ problem.

> Another question: What about the btuart_cs.ko module, what's the
> difference to the hci_uart module?

It only supports H:4 and is very limited and no longer supported.

Regards

Marcel