From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcel Holtmann Date: Tue, 07 Feb 2006 22:25:53 +0000 Subject: Re: Bluetooth UDEV info like empty after hi2hci Message-Id: <1139351153.22790.66.camel@localhost> List-Id: References: <1139304358.7057.12.camel@pc-05.ycom.ch> In-Reply-To: <1139304358.7057.12.camel@pc-05.ycom.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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? Regards Marcel ------------------------------------------------------- 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&kid3432&bid#0486&dat1642 _______________________________________________ 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