From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bluetooth UDEV info like empty after hi2hci
Date: Tue, 07 Feb 2006 12:53:25 +0000 [thread overview]
Message-ID: <20060207125325.GA10208@vrfy.org> (raw)
In-Reply-To: <1139304358.7057.12.camel@pc-05.ycom.ch>
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&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
next prev parent reply other threads:[~2006-02-07 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 9:25 Bluetooth UDEV info like empty after hi2hci Alexandre Ghisoli
2006-02-07 12:53 ` Kay Sievers [this message]
2006-02-07 16:54 ` Andrey Borzenkov
2006-02-07 22:25 ` Marcel Holtmann
2006-02-08 2:47 ` Kay Sievers
2006-02-08 2:53 ` Marcel Holtmann
2006-02-08 17:01 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060207125325.GA10208@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).