[RFC] X Input Driver specification
daniel at fooishbar.org
Wed Apr 18 02:40:30 PDT 2007
On Wed, Apr 18, 2007 at 10:03:21AM +0930, Peter Hutterer wrote:
> On 12/04/2007, at 07:24 , Magnus Vigerlöf wrote:
> >Yeah, I've seen that too.. Eventually I think that should go into a
> >outside the X-server, so the evdev-driver doesn't steal the device
> >if another
> >driver should run the input device (does it? I can't say I
> >understand the
> evdev grabs the device with an ioctl call. not sure why though.
> hotplugging in the evdev driver is historical, evdev did it before X
> did. I think daniel has a changed evdev driver in the pipe.
The evdev driver grabs the device with an ioctl for two reasons: one, so
it has exclusive use of that device, and other servers can't use it;
two, so if for some reason /dev/input/mice gets added, the grab removes
the evdev device from the repeater, so you don't get doubled events.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: Digital signature
More information about the xorg