All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] udev rules entry for bluetooth mouse
Date: Tue, 07 Feb 2006 23:24:19 +0100	[thread overview]
Message-ID: <1139351059.22790.63.camel@localhost> (raw)
In-Reply-To: <1139331334.12556.3.camel@pc-05.ycom.ch>

Hi Alexandre,

> > Did you contact the hotplug team about this issue ?
> 
> I got the folowing answer from hotplug ML : 
> 
> Kay Sievers <kay.sievers@vrfy.org>
> 
> 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.

and we don't have a "struct device", because the current integration of
the Bluetooth subsystem is a class device under /sys/class. It seems we
need to wait until the /sys/device unification found its way into the
kernel.

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&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-02-07 22:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  9:33 [Bluez-users] udev rules entry for bluetooth mouse Charles Bueche
2006-02-02 10:38 ` Alexandre Ghisoli
2006-02-02 11:45   ` Charles Bueche
2006-02-07  9:15     ` Alexandre Ghisoli
2006-02-07 16:55     ` Alexandre Ghisoli
2006-02-07 22:24       ` Marcel Holtmann [this message]
2006-02-08 15:09         ` Charles Bueche
2006-02-09 12:50           ` Alexandre Ghisoli
2006-03-27 12:09           ` Charles Bueche

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=1139351059.22790.63.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.