On 11/15/2010 06:45 PM, Peter Hutterer wrote: > Can you publish the evdev patches you're using at the moment somewhere so I > can have a look (if it isn't in one of the RFC emails already, I'm a bit > behind). > > My motivation to make the valuator API so restricted was to prevent the > drivers from trying to be clever. They should just set the data they get, > pass it on to the server and be done with it.
The evdev patches are in the RFC emails. Essentially, evdev does lots of post-processing of data, such as turning an absolute device into a relative device. This requires saving all the values from evdev somewhere and recalling them later to do the transformation. So either we use masked valuators to manage all the state, or we have to duplicate masked valuators functionality in the driver just to handle the intermediate state. -- Chase _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
