Bug#365444: [EMAIL PROTECTED]: Re: [EMAIL PROTECTED]: Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node]]

2006-05-01 Thread Greg KH
On Mon, May 01, 2006 at 01:28:59PM -0600, Jeremy Nickurak wrote: > On Mon, May 01, 2006 at 09:00:29PM +0200, Marco d'Itri wrote: > > Can you discuss the issue with the upstream maintainer? > > I'm not sure I'd know who to discuss it with, or how to. Is there even a udev > mailing list/web page so

Bug#365444: [EMAIL PROTECTED]: Re: [EMAIL PROTECTED]: Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node]]

2006-05-01 Thread Jeremy Nickurak
> Are you sure that this is really the mouse device and not something else > this keyboard provides? Do you get only these two devices when you > connect the keyboard? We probably can't assume that "00" is a mouse, cause > according the HID spec it mean "no protocol" which can be anything. We may >

Bug#365444: [EMAIL PROTECTED]: Re: [EMAIL PROTECTED]: Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node]]

2006-05-01 Thread Jeremy Nickurak
On Mon, May 01, 2006 at 09:00:29PM +0200, Marco d'Itri wrote: > Can you discuss the issue with the upstream maintainer? I'm not sure I'd know who to discuss it with, or how to. Is there even a udev mailing list/web page somewhere for this sort of thing? -- Jeremy Nickurak -= Email/Jabber: [EMAI

Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node

2006-04-30 Thread Jeremy Nickurak
On Sun, Apr 30, 2006 at 05:53:26PM +0200, Marco d'Itri wrote: > In persistent-input.rules, please replace = with == in the SYSFS{...} > keys. Almost did it. The mouse compenent uses SYSFS{bInterfaceProtocol}=="00", so adding the following did the trick: BUS=="usb", SYSFS{bInterfaceClass}=="03",

Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node

2006-04-30 Thread Marco d'Itri
In persistent-input.rules, please replace = with == in the SYSFS{...} keys. -- ciao, Marco signature.asc Description: Digital signature

Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node

2006-04-30 Thread Jeremy Nickurak
On Sun, Apr 30, 2006 at 04:32:53PM +0200, Marco d'Itri wrote: > Please report the output of: > > udevinfo -a -p /class/input/input1/event1 > udevinfo -a -p /class/input/input2/event2 > > -- > ciao, > Marco [EMAIL PROTECTED]:~$ udevinfo -a -p /class/input/input1/event1 udevinfo starts with the

Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node

2006-04-30 Thread Marco d'Itri
Please report the output of: udevinfo -a -p /class/input/input1/event1 udevinfo -a -p /class/input/input2/event2 -- ciao, Marco signature.asc Description: Digital signature

Bug#365444: Mouse and keyboard evdev devices mapped by-id to same node

2006-04-29 Thread Jeremy Nickurak
Package: udev Version: 0.091-1 Severity: important I have a Logitech Elite keyboard, which has both keyboard and mouse components. Unfortunately, evdev's by-id matching automatically tries to represent both by the same evdev node: Keyboard: > agaeris:/home/atrus# udevtest /class/input/input1/ev