From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Jansen Date: Fri, 05 Oct 2001 18:43:14 +0000 Subject: Re: hotplug, input and XFree86 Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Friday 05 October 2001 19:46, you wrote: > For example, I have a Wacom USB tablet. Hotplug works well except > that the input subsystem is not yet integrated so I have to guess > which input device number is use by the tablet. A nice work-around for mice is to use /dev/input/mice instead of the pointer's device node, but it does not work with other input devices. > So I propose to develop a generic 'input' driver for > XFree86. This input driver will only understand a subset > of the kernel-input events corresponding more or less > to the native X11 events (motions in n-dimensions, > n-buttons press/release and key press/release). 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/ > 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? bye... _______________________________________________ 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