2011-04-19 02:54:08

by Hui Zhu

[permalink] [raw]
Subject: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

Cannot connect to any outside devices through bluetooth.

And I think this is not a bug of low level driver. Because both my
laptop and a usb bluetooth card cannot work.

Thanks,
Hui


2011-04-19 03:05:58

by Wanlong Gao

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On 4/19/11, Hui Zhu <[email protected]> wrote:
> Cannot connect to any outside devices through bluetooth.
>
> And I think this is not a bug of low level driver. Because both my
> laptop and a usb bluetooth card cannot work.
>
> Thanks,
> Hui
Maybe this patch can fix ?
http://userweb.kernel.org/~akpm/mmotm/broken-out/bluetooth-fix-build-warnings-on-defconfigs.patch
> --
> 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/
>

2011-04-19 05:12:16

by Hui Zhu

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

I don't think so.

I am in x86_32 and x86_64.

Thanks,
Hui

On Tue, Apr 19, 2011 at 11:05, Wanlong Gao <[email protected]> wrote:
> On 4/19/11, Hui Zhu <[email protected]> wrote:
>> Cannot connect to any outside devices through bluetooth.
>>
>> And I think this is not a bug of low level driver. ?Because both my
>> laptop and a usb bluetooth card cannot work.
>>
>> Thanks,
>> Hui
> Maybe this patch can fix ?
> http://userweb.kernel.org/~akpm/mmotm/broken-out/bluetooth-fix-build-warnings-on-defconfigs.patch
>> --
>> 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/
>>
>

2011-04-19 07:26:36

by Wanlong Gao

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On 4/19/11, Hui Zhu <[email protected]> wrote:
> I don't think so.
>
> I am in x86_32 and x86_64.
>
> Thanks,
> Hui
So, you can copy your config file to the mail list , maybe some logs .
It will be more helpful to your issue .

Thanks
Wanlong
>
> On Tue, Apr 19, 2011 at 11:05, Wanlong Gao <[email protected]> wrote:
>> On 4/19/11, Hui Zhu <[email protected]> wrote:
>>> Cannot connect to any outside devices through bluetooth.
>>>
>>> And I think this is not a bug of low level driver. Because both my
>>> laptop and a usb bluetooth card cannot work.
>>>
>>> Thanks,
>>> Hui
>> Maybe this patch can fix ?
>> http://userweb.kernel.org/~akpm/mmotm/broken-out/bluetooth-fix-build-warnings-on-defconfigs.patch
>>> --
>>> 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/
>>>
>>
>


--
Best regards
Wanlong Gao

2011-04-19 07:46:20

by Dave Young

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
> Cannot connect to any outside devices through bluetooth.
>
> And I think this is not a bug of low level driver.  Because both my
> laptop and a usb bluetooth card cannot work.

Hi, please explain the "cannot work" in detail,
Firstly check dmesg and hciconfig to see if there's anything wrong.

--
Regards
dave

2011-04-19 15:34:51

by Hui Zhu

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

Do you part is OK?

I think it will be very easy to reproduce.

Thanks,
Hui

On Tue, Apr 19, 2011 at 15:46, Dave Young <[email protected]> wrote:
> On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
>> Cannot connect to any outside devices through bluetooth.
>>
>> And I think this is not a bug of low level driver. ?Because both my
>> laptop and a usb bluetooth card cannot work.
>
> Hi, please explain the "cannot work" in detail,
> Firstly check dmesg and hciconfig to see if there's anything wrong.
>
> --
> Regards
> dave
>

2011-04-24 13:52:22

by Ed Tomlinson

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On Tuesday 19 April 2011 11:34:30 Hui Zhu wrote:
> Do you part is OK?
>
> I think it will be very easy to reproduce.
>
> Thanks,
> Hui
>
> On Tue, Apr 19, 2011 at 15:46, Dave Young <[email protected]> wrote:
> > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
> >> Cannot connect to any outside devices through bluetooth.
> >>
> >> And I think this is not a bug of low level driver. Because both my
> >> laptop and a usb bluetooth card cannot work.
> >
> > Hi, please explain the "cannot work" in detail,
> > Firstly check dmesg and hciconfig to see if there's anything wrong.

I am also seeing problems with bluetooth in .39-rc4+

[54511.033258] usb 2-4.4: USB disconnect, device number 5
[54513.920060] usb 2-4.3: new full speed USB device number 6 using ehci_hcd
[54514.063057] usb 2-4.3: New USB device found, idVendor=0a12, idProduct=0001
[54514.070281] usb 2-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
grover ~ # hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:0A:3A:55:07:5A ACL MTU: 192:8 SCO MTU: 64:8
DOWN
RX bytes:718 acl:0 sco:0 events:25 errors:0
TX bytes:108 acl:0 sco:0 commands:24 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: CONFIG_BT_HCIBTUSB=m
Link mode: SLAVE ACCEPT

grover ~ # hciconfig hci0 up
Can't init device hci0: Invalid argument (22)

The same error happens If I just try a hciconfig hci0 up after boot (without replugging the adaptor).

CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
# CONFIG_BT_HCIUART_ATH3K is not set
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m

and bluez-4.91 is installed

Ideas?
Ed Tomlinson

2011-04-26 16:13:22

by Gustavo Padovan

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

* Ed Tomlinson <[email protected]> [2011-04-24 09:52:14 -0400]:

> On Tuesday 19 April 2011 11:34:30 Hui Zhu wrote:
> > Do you part is OK?
> >
> > I think it will be very easy to reproduce.
> >
> > Thanks,
> > Hui
> >
> > On Tue, Apr 19, 2011 at 15:46, Dave Young <[email protected]> wrote:
> > > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
> > >> Cannot connect to any outside devices through bluetooth.
> > >>
> > >> And I think this is not a bug of low level driver. Because both my
> > >> laptop and a usb bluetooth card cannot work.
> > >
> > > Hi, please explain the "cannot work" in detail,
> > > Firstly check dmesg and hciconfig to see if there's anything wrong.
>
> I am also seeing problems with bluetooth in .39-rc4+
>
> [54511.033258] usb 2-4.4: USB disconnect, device number 5
> [54513.920060] usb 2-4.3: new full speed USB device number 6 using ehci_hcd
> [54514.063057] usb 2-4.3: New USB device found, idVendor=0a12, idProduct=0001
> [54514.070281] usb 2-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> grover ~ # hciconfig -a
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:0A:3A:55:07:5A ACL MTU: 192:8 SCO MTU: 64:8
> DOWN
> RX bytes:718 acl:0 sco:0 events:25 errors:0
> TX bytes:108 acl:0 sco:0 commands:24 errors:0
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: CONFIG_BT_HCIBTUSB=m
> Link mode: SLAVE ACCEPT
>
> grover ~ # hciconfig hci0 up
> Can't init device hci0: Invalid argument (22)

does dmesg show something? I'm using a -rc kernel and bluetooth is working to
me.

--
Gustavo F. Padovan
http://profusion.mobi

2011-04-27 02:55:25

by Dave Young

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On Sun, Apr 24, 2011 at 9:52 PM, Ed Tomlinson <[email protected]> wrote:
> On Tuesday 19 April 2011 11:34:30 Hui Zhu wrote:
>> Do you part is OK?
>>
>> I think it will be very easy to reproduce.
>>
>> Thanks,
>> Hui
>>
>> On Tue, Apr 19, 2011 at 15:46, Dave Young <[email protected]> wrote:
>> > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
>> >> Cannot connect to any outside devices through bluetooth.
>> >>
>> >> And I think this is not a bug of low level driver.  Because both my
>> >> laptop and a usb bluetooth card cannot work.
>> >
>> > Hi, please explain the "cannot work" in detail,
>> > Firstly check dmesg and hciconfig to see if there's anything wrong.
>
> I am also seeing problems with bluetooth in .39-rc4+
>
> [54511.033258] usb 2-4.4: USB disconnect, device number 5
> [54513.920060] usb 2-4.3: new full speed USB device number 6 using ehci_hcd
> [54514.063057] usb 2-4.3: New USB device found, idVendor=0a12, idProduct=0001
> [54514.070281] usb 2-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> grover ~ # hciconfig -a
> hci0:   Type: BR/EDR  Bus: USB
>        BD Address: 00:0A:3A:55:07:5A  ACL MTU: 192:8  SCO MTU: 64:8
>        DOWN
>        RX bytes:718 acl:0 sco:0 events:25 errors:0
>        TX bytes:108 acl:0 sco:0 commands:24 errors:0
>        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>        Link policy: CONFIG_BT_HCIBTUSB=m
>        Link mode: SLAVE ACCEPT
>
> grover ~ # hciconfig hci0 up
> Can't init device hci0: Invalid argument (22)
>
> The same error happens If I just try a hciconfig hci0 up after boot (without replugging the adaptor).

I did not see your problem, my usb dongle usbid is 0a12:0001 as well,
maybe bisect is the way to go.

>
> CONFIG_BT_HCIBTSDIO=m
> CONFIG_BT_HCIUART=m
> CONFIG_BT_HCIUART_H4=y
> CONFIG_BT_HCIUART_BCSP=y
> # CONFIG_BT_HCIUART_ATH3K is not set
> CONFIG_BT_HCIUART_LL=y
> CONFIG_BT_HCIBCM203X=m
> CONFIG_BT_HCIBPA10X=m
> CONFIG_BT_HCIBFUSB=m
> CONFIG_BT_HCIVHCI=m
>
> and bluez-4.91 is installed
>
> Ideas?
> Ed Tomlinson
>



--
Regards
dave

2011-04-27 10:57:56

by Ed Tomlinson

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On Tuesday 26 April 2011 12:13:30 Gustavo F. Padovan wrote:
> * Ed Tomlinson <[email protected]> [2011-04-24 09:52:14 -0400]:
>
> > On Tuesday 19 April 2011 11:34:30 Hui Zhu wrote:
> > > Do you part is OK?
> > >
> > > I think it will be very easy to reproduce.
> > >
> > > Thanks,
> > > Hui
> > >
> > > On Tue, Apr 19, 2011 at 15:46, Dave Young <[email protected]> wrote:
> > > > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
> > > >> Cannot connect to any outside devices through bluetooth.
> > > >>
> > > >> And I think this is not a bug of low level driver. Because both my
> > > >> laptop and a usb bluetooth card cannot work.
> > > >
> > > > Hi, please explain the "cannot work" in detail,
> > > > Firstly check dmesg and hciconfig to see if there's anything wrong.
> >
> > I am also seeing problems with bluetooth in .39-rc4+
> >
> > [54511.033258] usb 2-4.4: USB disconnect, device number 5
> > [54513.920060] usb 2-4.3: new full speed USB device number 6 using ehci_hcd
> > [54514.063057] usb 2-4.3: New USB device found, idVendor=0a12, idProduct=0001
> > [54514.070281] usb 2-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > grover ~ # hciconfig -a
> > hci0: Type: BR/EDR Bus: USB
> > BD Address: 00:0A:3A:55:07:5A ACL MTU: 192:8 SCO MTU: 64:8
> > DOWN
> > RX bytes:718 acl:0 sco:0 events:25 errors:0
> > TX bytes:108 acl:0 sco:0 commands:24 errors:0
> > Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> > Link policy: CONFIG_BT_HCIBTUSB=m
> > Link mode: SLAVE ACCEPT
> >
> > grover ~ # hciconfig hci0 up
> > Can't init device hci0: Invalid argument (22)
>
> does dmesg show something? I'm using a -rc kernel and bluetooth is working to
> me.

What dmesg shows is included above. The tell tail for this bug is the error 22 from
user space. I see nothing on the kernel side.

Ed

2011-04-27 11:00:35

by Ed Tomlinson

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On Tuesday 26 April 2011 22:55:22 Dave Young wrote:
> On Sun, Apr 24, 2011 at 9:52 PM, Ed Tomlinson <[email protected]> wrote:
> > On Tuesday 19 April 2011 11:34:30 Hui Zhu wrote:
> >> Do you part is OK?
> >>
> >> I think it will be very easy to reproduce.
> >>
> >> Thanks,
> >> Hui
> >>
> >> On Tue, Apr 19, 2011 at 15:46, Dave Young <[email protected]> wrote:
> >> > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <[email protected]> wrote:
> >> >> Cannot connect to any outside devices through bluetooth.
> >> >>
> >> >> And I think this is not a bug of low level driver. Because both my
> >> >> laptop and a usb bluetooth card cannot work.
> >> >
> >> > Hi, please explain the "cannot work" in detail,
> >> > Firstly check dmesg and hciconfig to see if there's anything wrong.
> >
> > I am also seeing problems with bluetooth in .39-rc4+
> >
> > [54511.033258] usb 2-4.4: USB disconnect, device number 5
> > [54513.920060] usb 2-4.3: new full speed USB device number 6 using ehci_hcd
> > [54514.063057] usb 2-4.3: New USB device found, idVendor=0a12, idProduct=0001
> > [54514.070281] usb 2-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > grover ~ # hciconfig -a
> > hci0: Type: BR/EDR Bus: USB
> > BD Address: 00:0A:3A:55:07:5A ACL MTU: 192:8 SCO MTU: 64:8
> > DOWN
> > RX bytes:718 acl:0 sco:0 events:25 errors:0
> > TX bytes:108 acl:0 sco:0 commands:24 errors:0
> > Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> > Link policy: CONFIG_BT_HCIBTUSB=m
> > Link mode: SLAVE ACCEPT
> >
> > grover ~ # hciconfig hci0 up
> > Can't init device hci0: Invalid argument (22)
> >
> > The same error happens If I just try a hciconfig hci0 up after boot (without replugging the adaptor).
>
> I did not see your problem, my usb dongle usbid is 0a12:0001 as well,
> maybe bisect is the way to go.

I can try but this bug was introduced during the .38 to rc1 window. I've not had much luck
bisecting through pre rc1...

Is there any good way to trace what is giving the 'Invalid argument 22'?

Ed

> >
> > CONFIG_BT_HCIBTSDIO=m
> > CONFIG_BT_HCIUART=m
> > CONFIG_BT_HCIUART_H4=y
> > CONFIG_BT_HCIUART_BCSP=y
> > # CONFIG_BT_HCIUART_ATH3K is not set
> > CONFIG_BT_HCIUART_LL=y
> > CONFIG_BT_HCIBCM203X=m
> > CONFIG_BT_HCIBPA10X=m
> > CONFIG_BT_HCIBFUSB=m
> > CONFIG_BT_HCIVHCI=m
> >
> > and bluez-4.91 is installed
> >
> > Ideas?
> > Ed Tomlinson
> >
>
>
>
>

2011-04-30 10:40:07

by Milan Oravec

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

Hui Zhu <teawater <at> gmail.com> writes:

>
> Cannot connect to any outside devices through bluetooth.
>
> And I think this is not a bug of low level driver. Because both my
> laptop and a usb bluetooth card cannot work.
>
> Thanks,
> Hui
>

Hi, I have the same problem here. My usb blue-tooth dongle can not be enabled up
in .39 kernel series.

In 2.6.38.x and earlier it works fine.

Anny suggestions?

Thank you very much.

Best regards Milan.

2011-05-05 12:45:10

by Milan Oravec

[permalink] [raw]
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

Hi, any news/solutions for this bug? It is still present in 2.6.39-rc6:

root@migo:/home/migo# hciconfig hci0 up
Can't init device hci0: Invalid argument (22)
root@migo:/home/migo# hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:10:60:A2:49:1C ACL MTU: 192:8 SCO MTU: 64:8
DOWN
RX bytes:1424 acl:0 sco:0 events:48 errors:0
TX bytes:216 acl:0 sco:0 commands:48 errors:0

root@migo:/home/migo# uname -a
Linux migo 2.6.39-rc6 #6 SMP PREEMPT Wed May 4 19:28:05 CEST 2011 i686
GNU/Linux
root@migo:/home/migo# lsusb -v

....

Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a12 Cambridge Silicon Radio, Ltd
idProduct 0x0001 Bluetooth Dongle (HCI mode)
bcdDevice 5.25
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 193
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 0
iInterface 0
Device Firmware Upgrade Interface Descriptor:
bLength 7
bDescriptorType 33
bmAttributes 7
Will Not Detach
Manifestation Tolerant
Upload Supported
Download Supported
wDetachTimeout 5000 milliseconds
wTransferSize 1023 bytes
Device Status: 0x0001
Self Powered

....

Thanks Milan