Andreas Wrede wrote:
> I am trying to get a D-Link DBT-120 bluetooth adapter to attach to the 
> new bluetooth stack and am having no luck.
> 
> I built a 4.0_BETA/i386 GENERIC kernel, src from today.  When inserting 
> the DBT-120, I get the following messages:
> 
> uhidev0 at uhub0 port 2 configuration 1 interface 0
> uhidev0: Cambridge Silicon Radio product id 0x1000, rev 2.00/15.86, addr 
> 2, iclass 3/1
> ukbd0 at uhidev0
> wskbd1 at ukbd0 mux 1
> wskbd1: connecting to wsdisplay0
> uhidev1 at uhub0 port 2 configuration 1 interface 1
> uhidev1: Cambridge Silicon Radio product id 0x1000, rev 2.00/15.86, addr 
> 2, iclass 3/1
> ums0 at uhidev1: 5 buttons
> wsmouse1 at ums0 mux 0
> uhidev0: at uhub0 port 2 (addr 2) disconnected
> wskbd1: disconnecting from wsdisplay0
> wskbd1 detached
> ukbd0 detached
> uhidev0 detached
> uhidev1: at uhub0 port 2 (addr 2) disconnected
> wsmouse1 detached
> ums0 detached
> uhidev1 detached
> uhidev0 at uhub0 port 2 configuration 1 interface 0
> uhidev0: Cambridge Silicon Radio product id 0x1000, rev 2.00/15.86, addr 
> 2, iclass 3/1
> ukbd0 at uhidev0
> wskbd1 at ukbd0 mux 1
> wskbd1: connecting to wsdisplay0
> uhidev1 at uhub0 port 2 configuration 1 interface 1
> uhidev1: Cambridge Silicon Radio product id 0x1000, rev 2.00/15.86, addr 
> 2, iclass 3/1
> ums0 at uhidev1: 5 buttons
> wsmouse1 at ums0 mux 0
> 
> I have an older D-Link DWB-120, which attaches as follows:
> 
> ubt0 at uhub0 port 2 configuration 1 interface 0
> ubt0: Broadcom BCM2033 (no firmware), rev 1.01/0.a0, addr 2
> 
> (The Broadcom firmware load device is broken, I am sending a pr)
> 
> Where is the decision made to which kernel device a new USB device 
> attaches and/or how do I get it to attach to ubt?

The device reports itself. So either you don't have a bluetooth device, 
or the thing is broken, or the thing needs quirks, or ...