From: Charles Bueche <charles@bueche.ch>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] udev rules entry for bluetooth mouse
Date: Thu, 02 Feb 2006 10:33:25 +0100 [thread overview]
Message-ID: <1138872805.21953.20.camel@bluez.bueche.ch> (raw)
Hi,
I would like my new Logitech V270 to exists under /dev/input/v270,
instead of a changing /dev/input/mouseN.
The goal is to be able to use one of the Logitech control utilities,
which need a device to operate on.
% hidd --show
00:07:61:3B:9B:7C Logitech Bluetooth Mouse [046d:b002] connected
% cat /proc/bus/input/devices
...snipp...
I: Bus=0005 Vendor=046d Product=b002 Version=4809
N: Name="Logitech Bluetooth Mouse"
P: Phys=00:10:C6:22:54:AF
H: Handlers=mouse4 event4
B: EV=f
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: ABS=300 0
...snipp...
How does this translate to a udev rule ? My attempts so far are failing.
Charles
--
Charles Bueche <charles@bueche.ch>
sand, snow, wave, wind and net -surfer
-------------------------------------------------------
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
next reply other threads:[~2006-02-02 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 9:33 Charles Bueche [this message]
2006-02-02 10:38 ` [Bluez-users] udev rules entry for bluetooth mouse 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
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=1138872805.21953.20.camel@bluez.bueche.ch \
--to=charles@bueche.ch \
--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 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).