From: Vojtech Pavlik <vojtech@suse.cz>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug, input and XFree86
Date: Sat, 06 Oct 2001 09:45:54 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100236162532497@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100229087228546@msgid-missing>
On Sat, Oct 06, 2001 at 09:35:32AM +0000, Stephane Chauveau wrote:
> 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.
It should be back alive now. Dan Skarda told me he's resuming the work
on 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.
True. This, unfortunately, can't be fixed or worked around easily.
--
Vojtech Pavlik
SuSE Labs
_______________________________________________
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
prev parent reply other threads:[~2001-10-06 9:45 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
2001-10-06 7:39 ` Stephane Chauveau
2001-10-06 9:45 ` Vojtech Pavlik [this message]
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-100236162532497@msgid-missing \
--to=vojtech@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).