Re: Bluetooth UDEV info like empty after hi2hci

[Kay Sievers <kay.sievers@vrfy.org>]

On Tue, Feb 07, 2006 at 11:25:53PM +0100, Marcel Holtmann wrote:
> Hi Kay,
> 
> > > I've asked this on bluetooth mailing list, but I cannot see if this
> > > issue come from UDEV or Bluetooth stack.
> > 
> > > --cut--
> > >   looking at device '/class/input/input4/mouse1':
> > >     KERNEL="mouse1"
> > >     SUBSYSTEM="input"
> > >     SYSFS{dev}="13:33"
> > > 
> > >   looking at device '/class/input/input4':
> > >     ID="input4"
> > >     BUS="input"
> > >     DRIVER=""
> > >     SYSFS{uniq}=""
> > >     SYSFS{phys}=""
> > >     SYSFS{name}="Bluetooth HID Boot Protocol Device"
> > 
> > The kernel driver needs to set the "struct device", to get a "device" link
> > in sysfs pointing to the physical device, otherwise the USB devices are not
> > reachable and udev can't match.
> 
> I would love to do that, but the Bluetooth subsystem is only available
> under /sys/class at the moment. So which "struct device" should I use?

Ah, ok. The Bluetooth "bus" never happened, right? I just remember we
talked about that last year with David in Ottawa. :) Passing the usb
"device" behind the hci would not be correct, right?

Cheers,
Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel