Bug#359003: [Pkg-bluetooth-maintainers] Bug#359003: bluez-utils: udev script missing

[Hadmut Danisch]

Edd Dumbill wrote:
> Please include the output of lsusb -v so we can see the make and model
> of your dongle


Bus 002 Device 003: 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            4.43
   iManufacturer           0
   iProduct                0
   iSerial                 0
   bNumConfigurations      1


It is a D-Link Bluetooth DBT-120.

I have another notebook at work with builtin bluetooth. When switching 
radio on (WLAN+Bluetooth) with the radio switch at the front this has 
the effect as if a Bluetooth USB dongle had been inserted. I'll send 
those USB data tomorrow.

However, wouldn't it be easier to just take the Vendor/Product id list 
from the driver software? If the dongle driver can use it, there must be 
a list of recognized dongles (or Vendor/Product ids). Why not use that 
already existing list?


regards
Hadmut