-------------- Original message ----------------------
From: Marcel Holtmann <[EMAIL PROTECTED]>
> Hi Quel,
>
> > Bad news: I still cannot use the device.
> >
> > hcitool inq, hcitool scan, hcitool name <btaddr> and hcitool info
> > <btaddr>
> > commands work.
> >
> > hcitool cc <btaddr>, sdptool <btaddr>, rfcomm connect command fail,
> > most of them
> > with a 'Connection reset by peer' error.
>
> what does "hciconfig hci0 version" tell you about your device? Some of
> the none major based Bluetooth chips are broken and might need an
> extra tweak within the USB driver.
>
Marcel,
# hciconfig hci0 version
hci0: Type: USB
BD Address: 00:03:0D:00:15:47 ACL MTU: 192:8 SCO MTU: 64:8
HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: 0xbc
Manufacturer: Cambridge Silicon Radio (10)
# lsusb | grep Cambridge
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
This device works fine in 2.6.23.1 and got broken circa 2.6.24 rcs.
Thank you,
--
kk1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
