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...
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"
EndDeviceDescThe 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.
Obviously, if you have more than one device with the same description,
a) You need something to further differentiate the units. Perhaps something like "SerialNum xxx " or "modelNum yyy ", or just "FirstOne".
b) If there is a lack of differentiating data, then 1-to-many devices are mapped to 1-to-many instances of the same driver. Have to do something at the identifier to uniquely ID them -- appending an incrementing integer works.
Thoughts? Flames? Arguments? I like 'em...
-- ____ .:. ____ Bryan W. Headley - [EMAIL PROTECTED]
_______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
