Re: hotplug, input and XFree86

[Stephane Chauveau <s.chauveau@chello.nl>]

On 2001.10.05 18:43 Tim Jansen wrote:
> 
> There is a input driver, using the event interface. It has to be ported
> to 
> XFree 4.0 though.
> 
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linuxconsole/ruby/xfree86/
> http://sourceforge.net/projects/linuxconsole/
> 

Interesting. Is the project still alive? Nothing has been updated for 
almost a year. Anyway, I will have a look to it. 

> 
> > The daemon will be responsible for
> >   - Creating one or more devices (daemon device) for each
> >     physical device  that could be plugged in the system
> >     Those file devices can be opened by the XFree86 generic 'input'
> >     driver even if the physical device is yet not plugged in.
> >   - respond to hotplug requests by mapping those demon daemon devices
> >     to the kernel input devices.
> >   - translate kernel input events to XFree86 input events
> >     and redirect them to the appropriate daemon device.
> 
> Why don't you implement the ability to deal with disappearing devices  in
> the 
> input driver itself?


I have not investigated a lot but I believe that there is a major 
problem with the XInput protocol and with the way XFree86 is 
designed.
They both seem to assume that the list of devices is static. 
For example, XInput does not provide any events to inform the 
clients that a device has been added or removed. 





_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel