From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 07 Feb 2006 12:53:25 +0000 Subject: Re: Bluetooth UDEV info like empty after hi2hci Message-Id: <20060207125325.GA10208@vrfy.org> 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 On Tue, Feb 07, 2006 at 10:25:58AM +0100, Alexandre Ghisoli wrote: > Hi, > > 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. 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&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