From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bluetooth UDEV info like empty after hi2hci
Date: Wed, 08 Feb 2006 17:01:38 +0000 [thread overview]
Message-ID: <20060208170138.GA21244@vrfy.org> (raw)
In-Reply-To: <1139304358.7057.12.camel@pc-05.ycom.ch>
On Wed, Feb 08, 2006 at 03:53:12AM +0100, Marcel Holtmann wrote:
> > > > > 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?
>
> I got convinced that keeping them as class device is better and once the
> unified /sys/devices/ got merged we re-evaluate it.
Yeah, may make sense, even when it will not be that different for the
driver core users in the first run. It will just look a bit different for
userspace.
> Since not every Bluetooth device is attached over USB it might be kinda
> not the right way. However such a workaround can be used for now. Will
> this really work and not cause more troubles?
It should work without trouble, yes. But sure, it may not be worth the effort,
when it will change again later this year. So it should be fine for now to plug
in a shell script in the udev process and lookup that information from
somewhere else.
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
prev parent reply other threads:[~2006-02-08 17:01 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
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 [this message]
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=20060208170138.GA21244@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).