All of lore.kernel.org
 help / color / mirror / Atom feed
From: a2@adamis.de
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Once again: Socket CF card and Kernel 2.6
Date: Mon, 28 Feb 2005 23:02:09 +0100	[thread overview]
Message-ID: <20050228220209.GA8151@adamis.de> (raw)
In-Reply-To: <1109578431.17256.9.camel@pegasus>

Hi Marcel,

On 28.02.05 09:13:51, Marcel Holtmann wrote:
> > I'm trying to install a Socket Bluetooth Compactflash Card (Revision H)
> > in my Thinkpad X21. I tested it with the 2.4.29 kernel (from Debian
> > unstable) and it works, but I would like to use 2.6 and there it doesn't
> > work.
> > 
> > With 2.6, the serial_cs module gets loaded as I insert the card and
> > dmesg shows the following:
> > 
> > -----
> > ttyS1: detected caps 00000700 should be 00000100
> > ttyS1 at I/O 0x2f8 (irq = 11) is a 16C950/954
> > -----
> > 
> > Then I run modprobe hci_uart and this is what dmesg says:
> > 
> > -----
> > Bluetooth: HCI UART driver ver 2.1
> > Bluetooth: HCI BCSP protocol initialized
> > -----
> > (I didn't include CONFIG_BT_HCIUART_H4 in my kernel this time)
> > 
> > No problem so far, but then:  hciattach ttyS1 socket
> > and it says "BCSP initialization timed out" and hcitool dev doesn't show
> > any devices.
> 
> 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...

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

Thanks in advance

Mathias

-- 
http://www.adamis.de/adam/
Es gibt mehr Leute, die kapitulieren, als solche, die scheitern.
 - Henry Ford


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-28 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26  3:19 [Bluez-users] Once again: Socket CF card and Kernel 2.6 Mathias Adam
2005-02-28  8:13 ` Marcel Holtmann
2005-02-28 22:02   ` a2 [this message]
2005-03-01  8:29     ` Marcel Holtmann
2005-03-05  5:37       ` Mathias Adam
2005-03-05  9:17         ` Erwin Authried
2005-03-05 14:42           ` Mathias Adam
2005-03-05 11:24         ` Marcel Holtmann
2005-03-05 14:18           ` Mathias Adam
2005-03-05 14:35             ` Mathias Adam
2005-03-05 18:17             ` Marcel Holtmann
2005-03-05 19:25               ` Mathias Adam
2005-03-05 19:55                 ` Marcel Holtmann
2005-03-06 19:37                   ` Mathias Adam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050228220209.GA8151@adamis.de \
    --to=a2@adamis.de \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.