input devices

input devices

[Marco d'Itri]

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?

-- 
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_id\x1278&alloc_id371&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

input devices

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: input devices

[Kay Sievers]

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

Re: input devices

[Johannes Berg]

On Fr, 2005-03-25 at 02:50 +0100, Kay Sievers wrote:

> 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



-------------------------------------------------------
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