[RFC] X Input Driver specification

Tue Apr 17 17:33:21 PDT 2007

On 12/04/2007, at 07:24 , Magnus Vigerlöf wrote:
> That's good to hear. Should I update the wiki with this info? I.e. 
> do you
> think the content and layout is good enough, or could it be 
> presented in a
> better way?

put it up. I deal mostly with event delivery, so I'm not sure how it 
can be presented better.
> Yeah, I've seen that too.. Eventually I think that should go into a 
> program
> 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
> code...)

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.
> Since I suspect UnInit has never been called by the Xserver, ever, 
> that would
> apply to all input driver maintainers... Let's start with saying 
> that there's
> no input driver that supports hot-plugging (ok, all manages 
> plugging but what
> about unplugging?) and then take them as they are requested/...

I suppose UnInit() should go into CloseDevice() then.
Cheers,
 Peter
--
Multi-Pointer X Server
http://wearables.unisa.edu.au/mpx