On Wed, Jan 25, 2006 at 05:03:52PM +0100, Andreas Schuldei wrote: > i have here a system witch runs two Xservers, has two heads with > two displays, two keyboards and two mice. > > I used to use the evdev driver and identified my devices like > this: > Option "Dev Name" "ELECOM ELECOM image sensor mouse > with wheel" > > note the cool name whith which i could identify it easily by its > internal name. Alternatively i could give the device path like > this: > > # Option "Dev Phys" "usb-0000:00:02.3-1.1/input0" > > now the new driver requires a device file. how do you recommend > to do that, so that the mice and keyboards are told apart > reliably?
Use a udev rule. > I am curious: why wasn't our (superior?) driver integrated > upstream instead? it seemed more feature full and usefull. For various reasons, it was felt that evdev warranted its own driver, instead of being hacked into the kbd/mouse drivers which were already bloated with random code. The normal evdev is getting there; there are patches for XKB support, f.e. Cheers, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
