new bluetooth id for lenovo T410s?

new bluetooth id for lenovo T410s?

[Martin Vogt]

Hello,

I have a new Lenovo T410s with the compat-wireless package for 2.6.34.

My bluetooh chip seems not to work:

linux-4box:~ # lsusb | grep Broadcom
Bus 001 Device 005: ID 0a5c:217f Broadcom Corp.

This device id (from lsub) is missing in ./drivers/bluetooth/btusb.c:

/* IBM/Lenovo ThinkPad with Broadcom chip */
{ USB_DEVICE(0x0a5c, 0x201e), .driver_info = BTUSB_WRONG_SCO_MTU },
{ USB_DEVICE(0x0a5c, 0x2110), .driver_info = BTUSB_WRONG_SCO_MTU },

Most likely the T410s has this chip onboard:

Broadcom Model: BCM2045B (BDC-2).

But I haven't found any resources on the lenovo pages about that.
Only this:

http://www.thinkwiki.org/wiki/ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)

Do you think I should add the ids to btusb.c?

+{ USB_DEVICE(0x0a5c, 0x217f), .driver_info = BTUSB_WRONG_SCO_MTU },

and test it?

regards,

Martin

Re: new bluetooth id for lenovo T410s?

[Marcel Holtmann]

Hi Martin,

so first of all, this is the wrong mailing list. You should be using
linux-bluetooth@vger.kernel.org.

> I have a new Lenovo T410s with the compat-wireless package for 2.6.34.
> 
> My bluetooh chip seems not to work:
> 
> linux-4box:~ # lsusb | grep Broadcom
> Bus 001 Device 005: ID 0a5c:217f Broadcom Corp.
> 
> This device id (from lsub) is missing in ./drivers/bluetooth/btusb.c:
> 
> /* IBM/Lenovo ThinkPad with Broadcom chip */
> { USB_DEVICE(0x0a5c, 0x201e), .driver_info = BTUSB_WRONG_SCO_MTU },
> { USB_DEVICE(0x0a5c, 0x2110), .driver_info = BTUSB_WRONG_SCO_MTU },

Please send in the output of /proc/bus/usb/devices for your devices
since I doubt it is not supported. There are general interface
descriptors that make the devices work. Only if Lenovo screwed something
up, then this is needed.

Regards

Marcel

Re: new bluetooth id for lenovo T410s?

[Martin Vogt]

Marcel Holtmann wrote:
> Hi Martin,
> 
> so first of all, this is the wrong mailing list. You should be using
> linux-bluetooth@vger.kernel.org.
Oh, ok.

> Please send in the output of /proc/bus/usb/devices for your devices
> since I doubt it is not supported. There are general interface
> descriptors that make the devices work. Only if Lenovo screwed something
> up, then this is needed.
> 

Just a small update: It works now, the btusb driver
from the compat-wireless module didnt load with symbol
problems.
(I use a Suse 2.6.27 vendor kernel which already is a bit 2.6.28+
compat-wireless-2.6.34)

I placed some #if 0 #endif combinations in compat-2.6.28.c
==>now it works.

regards,

Martin

Re: new bluetooth id for lenovo T410s?

[Luis R. Rodriguez]

On Fri, May 28, 2010 at 3:40 AM, Martin Vogt
<martin.vogt@itwm.fraunhofer.de> wrote:
> Marcel Holtmann wrote:
>> Hi Martin,
>>
>> so first of all, this is the wrong mailing list. You should be using
>> linux-bluetooth@vger.kernel.org.
> Oh, ok.
>
>> Please send in the output of /proc/bus/usb/devices for your devices
>> since I doubt it is not supported. There are general interface
>> descriptors that make the devices work. Only if Lenovo screwed something
>> up, then this is needed.
>>
>
> Just a small update: It works now, the btusb driver
> from the compat-wireless module didnt load with symbol
> problems.
> (I use a Suse 2.6.27 vendor kernel which already is a bit 2.6.28+
> compat-wireless-2.6.34)
>
> I placed some #if 0 #endif combinations in compat-2.6.28.c
> ==>now it works.

Was this a Suse distribution problem? If so can you elaborate?

  Luis

Re: new bluetooth id for lenovo T410s?

[Martin Vogt]

Luis R. Rodriguez wrote:
> On Fri, May 28, 2010 at 3:40 AM, Martin Vogt
> <martin.vogt@itwm.fraunhofer.de> wrote:
>> Marcel Holtmann wrote:
>>> Hi Martin,
>>>
>>> so first of all, this is the wrong mailing list. You should be using
>>> linux-bluetooth@vger.kernel.org.
>> Oh, ok.

>>>
>> Just a small update: It works now, the btusb driver
>> from the compat-wireless module didnt load with symbol
>> problems.
>> (I use a Suse 2.6.27 vendor kernel which already is a bit 2.6.28+
>> compat-wireless-2.6.34)
>>
>> I placed some #if 0 #endif combinations in compat-2.6.28.c
>> ==>now it works.
> 
> Was this a Suse distribution problem? If so can you elaborate?
> 

I thought that bluetooth would not work an the T410, but
now Im not sure anymore, if it would have worked directly
with 2.6.27.suse.
(At least the KDE 3.5 bluetooth applet was "grey" (and is still grey),
the KDE 4.x kbluetooth app works now, but maybe
this would have worked before too...--dont know--)

So I cannot say if it wouldnt have worked out of the box
because I directly upgrade to compat-wireless 2.6.34.

regards,

Martin


This was the patch required for the vendor SUSE kernel.

--- compat/compat-2.6.28.c.org  2010-05-27 15:41:41.000000000 +0200
+++ compat/compat-2.6.28.c      2010-05-27 15:57:33.000000000 +0200
@@ -307,6 +307,7 @@
 }
 EXPORT_SYMBOL_GPL(pci_ioremap_bar);

+#if 0
 static unsigned long round_jiffies_common(unsigned long j, int cpu,
                bool force_up)
 {
@@ -369,5 +370,5 @@
        skb->truesize += size;
 }
 EXPORT_SYMBOL(skb_add_rx_frag);
-
+#endif /* vogt */
 #endif /* LINUX_VERSION_CODE < KERNEL_VERSION(2,6,28) */