From: Yan Seiner <yan@seiner.com>
To: linux-hotplug@vger.kernel.org
Subject: How to write this rule?
Date: Tue, 10 Feb 2009 15:19:32 +0000 [thread overview]
Message-ID: <49919B04.6040209@seiner.com> (raw)
I have a device that presents itself as both a /dev/input/mouise and
/dev/input/event.
The mouse:
looking at device '/class/input/input10/mouse6':
KERNEL="mouse6"
SUBSYSTEM="input"
DRIVER=""
looking at parent device '/class/input/input10':
KERNELS="input10"
SUBSYSTEMS="input"
DRIVERS=""
ATTRS{name}="HID 06b4:1c70"
ATTRS{phys}="usb-0000:00:02.1-4.4.4.4.4.1/input0"
ATTRS{uniq}=""
The event:
looking at device '/class/input/input10/event10':
KERNEL="event10"
SUBSYSTEM="input"
DRIVER=""
looking at parent device '/class/input/input10':
KERNELS="input10"
SUBSYSTEMS="input"
DRIVERS=""
ATTRS{name}="HID 06b4:1c70"
ATTRS{phys}="usb-0000:00:02.1-4.4.4.4.4.1/input0"
ATTRS{uniq}=""
The *only* difference between the two is the KERNEL= line. I need to
create a symlink to both the mouse and the event. I tried this:
# usb remote
KERNEL="event*", ENV{ID_CLASS}="event"
KERNEL="input*", ENV{ID_CLASS}="input"
ENV{ID_CLASS}="event", SUBSYSTEMS="input", ATTRS{name}="HID
06b4:1c70", ATTRS{phys}="usb-0000:00:02.1-4.4.4.4.4.1/input0", \
SYMLINK+="myth/remote", ENV{GENERATED}="1"
ENV{ID_CLASS}="input", SUBSYSTEMS="input", ATTRS{name}="HID
06b4:1c70", ATTRS{phys}="usb-0000:00:02.1-4.4.4.4.4.1/input0", \
SYMLINK+="myth/rmouse", ENV{GENERATED}="1"
But it doesn't work. I'm unclear on how to deal with this; I need to
somehow remember if I am looking at the event device or the mouse
device.... But how?
Thanks,
--Yan
next reply other threads:[~2009-02-10 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 15:19 Yan Seiner [this message]
2009-02-10 15:29 ` How to write this rule? Kay Sievers
2009-02-10 17:04 ` Yan Seiner
2009-02-10 17:09 ` 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=49919B04.6040209@seiner.com \
--to=yan@seiner.com \
--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).