From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: input devices
Date: Fri, 25 Mar 2005 01:50:23 +0000 [thread overview]
Message-ID: <1111715423.5062.2.camel@localhost.localdomain> (raw)
In-Reply-To: <marc-linux-hotplug-107219417225628@msgid-missing>
On Fri, 2005-03-25 at 00:30 +0100, Johannes Berg wrote:
> Hi,
>
> I have a PowerBook here that has has an internal USB
> keyboard/trackpad/consumer device (the consumer device is just the
> 'eject' button).
>
> Now I'd like to have a symlink from /dev/input/event2
> to /dev/input/internal-keyboard but I can't figure out how to configure
> udev to do this.
>
> I tried
> BUS="usb", SYSFS{idVendor}="05ac", SYSFS{idProduct}="020e", NAME="input/internal"
> but that gives me a device node (don't care if its a symlink or not) for
> event3 which is the eject button. Is it possible to differentiate
> between the three devices that are generated from this?
Try:
udevinfo -a -p /class/input/<device>
for the devices you want to match against. I will print the possible
keys you can use to write a rule. Look for something that distinguishes
one device from another.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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 prev parent reply other threads:[~2005-03-25 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 15:39 input devices Marco d'Itri
2005-03-24 23:30 ` Johannes Berg
2005-03-25 1:50 ` Kay Sievers [this message]
2005-03-25 2:33 ` Johannes Berg
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=1111715423.5062.2.camel@localhost.localdomain \
--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).