On Mon, Sep 29, 2003 at 09:52:16AM -0500, Bryan W. Headley wrote: >David, > >How is the work on the XF86Config parser coming? I ask because I noticed >that the 'Option "Device" "/dev/input/event?"' is getting weird, like I >thought it would when we were discussing Input System improvements. > >Specifically, my tablet seems to have chosen for it different >/dev/input/event? paths where it is mapped to during boot-up. For >several times, it's mapped to /dev/input/event2, then after a subsequent >reboot, it moves to /dev/input/event1 for awhile...
In the short term, can whatever daemon on Linux handles plug events be configured to point some symlink to the correct device? If so, you could refer to that in the XF86Config file? >Given that we're dealing with hotplug systems, and are now seeing a >series of device mappings to pseudo-devices (unlike, say, /dev/tty01, >which always refers to a specific serial port), I'm wondering if there >should be a different keyword in the Config file to augment "Device"... > >This is half-baked, so I'm throwing it out for comment for than anything: > >1. Device /path # same behavior as before >2. DeviceDesc > Bus "USB" > ID "Wacom" > EndDeviceDesc > >The notion here is, something that is matched to the operating system >will scan the 'pseudo-mapped' devices, knowing that it's looking for a >Wacom device on one of the USB ports. It should come back with an array >of paths (in case you have more than one tablet), which the device >driver loader then uses as it's path for opening the handle. In the current non-hotplug environment, one approach might be to enumerate input devices in a way analogous to what we do with video cards, and bind InputDevice sections to hardware with a similar method to that used for Device sections. This would at least allow you to say in your configuration that you want to use a wacom device, and the driver will bind to the "first" one. I've been doing some things to allow the mouse driver to automatically find a device without having to be told where to find it. But I'm looking at this stuff from the point of view of handling the most common user situations now, while working towards a more general solution rather than holding everything up until the general solution is worked through. David -- David Dawes X-Oz Technologies www.XFree86.org/~dawes www.x-oz.com _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
