All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug, input  and XFree86
Date: Fri, 05 Oct 2001 18:43:14 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100230732928849@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100229087228546@msgid-missing>

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

  parent reply	other threads:[~2001-10-05 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 14:07 hotplug, input and XFree86 Stephane Chauveau
2001-10-05 15:51 ` Stephane Chauveau
2001-10-05 18:43 ` Tim Jansen [this message]
2001-10-06  7:39 ` Stephane Chauveau
2001-10-06  9:45 ` Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-100230732928849@msgid-missing \
    --to=tim@tjansen.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.