From: Alexandre Ghisoli <alexandre.ghisoli@ycom.ch>
To: linux-hotplug@vger.kernel.org
Subject: Bluetooth UDEV info like empty after hi2hci
Date: Tue, 07 Feb 2006 09:25:58 +0000 [thread overview]
Message-ID: <1139304358.7057.12.camel@pc-05.ycom.ch> (raw)
Hi,
I've asked this on bluetooth mailing list, but I cannot see if this
issue come from UDEV or Bluetooth stack.
Linux 2.6.15
UDEV 084
DiNovo keyb and mice
I cannot force the device name in udev to link it in xorg
configuration file.
Fixed device name is required for the Xorg configuration, since kernel
and udev change device numbers at reconnect, after a Bluetooth stop to
save batteries.
Example :
/dev/input/event0 -> mouse at startup (in usb mode)
/dev/input/event1 -> keyboard (in usb mode)
/dev/input/event3 -> mouse in BT mode, if I touch mice first
/dev/input/event4 -> keyboard in BT mode
After a while without using mouse, hidd will stop session with device.
Touching the mouse re-enable the link, but device number could be
event5 !
So, I want to fix the device name with a udev script. Testing :
KERNEL="event[0-9]*" SYSFS{idVendor}="046d",
SYSFS{idProduct}="b001", NAME="input/ev-mx900", MODE="0664"
Not working !!
/proc/bus/input/devices gives :
I: Bus\005 Vendor\x046d Product°01 Version"00
N: Name="Bluetooth HID Boot Protocol Device"
P: PhysS: Sysfs=/class/input/input4
H: Handlers=mouse1 event4
B: EV=7
B: KEY=xxx
B: REL\x103
And UDEV has only :
udevinfo -a -p /sys/class/input/mouse1
--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"
This mean that the udev struct is not filled with all needed infos to
match udev rules.
Any help to make it working ?
-------------------------------------------------------
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 reply other threads:[~2006-02-07 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 9:25 Alexandre Ghisoli [this message]
2006-02-07 12:53 ` Bluetooth UDEV info like empty after hi2hci 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
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=1139304358.7057.12.camel@pc-05.ycom.ch \
--to=alexandre.ghisoli@ycom.ch \
--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).