input devices

DISCUSSION Marco d'Itri 3 participants 4 messages Dec 23, 2003 – Mar 25, 2005

Share & tools

Marco d'Itri

author

2003-12-23 15:39 UTC #0 lore raw

input.agent looks for a modules.inputmap, but I do not have it among the other other map files and module-init-tools does not know about it:

md@wonderland:~$ grep -r modules.inputmap /USR3/src/P/mit/module-init-tools-0.9.15-pre4/
md@wonderland:~$

Who is at fault?

Signature · 13 lines

ciao, |
Marco | [3743 imIvJ6TS9CLAk]


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Johannes Berg

2005-03-24 23:30 UTC #1 lore raw

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?

thanks,
johannes

Kay Sievers

2005-03-25 01:50 UTC #2 lore raw

In reply to Marco d'Itri

Quoted 10 lines · Johannes Berg

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.

Quoted 5 lines

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_id396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Johannes Berg

2005-03-25 02:33 UTC #3 lore raw

In reply to Marco d'Itri

Quoted 6 lines · Kay Sievers

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.

Neat, thanks. Unfortunately it seems that I can either differentiate between the two, or differentiate them from other keyboards as the only thing that tells them apart is in the following section which doesn't
have anything like the vendor ID etc.:
looking at the device chain at '/sys/devices/pci0001:10/0001:10:1a.0/usb2/2-2/2-2:1.0':

    BUS="usb"
    ID="2-2:1.0"
    DRIVER="usbhid"
    SYSFS{bAlternateSetting}=" 0"
    SYSFS{bInterfaceClass}="03"
    SYSFS{bInterfaceNumber}="00"
    SYSFS{bInterfaceProtocol}="01"
    SYSFS{bInterfaceSubClass}="01"
    SYSFS{bNumEndpoints}="01"
    SYSFS{detach_state}="0"
    SYSFS{interface}="Keyboard"

Anyway, I learned something about udev today :)

johannes