Input device design (3)

Johnson, Charles F charles.f.johnson at
Wed Aug 31 10:12:07 PDT 2005


We're exactly on the same page.  I'm going to be putting together a more
detailed written proposal and also a proof of concept prototype.


--Charles Johnson
Intel Corporation
charles.f.johnson at

>-----Original Message-----
>From: xorg-bounces at [mailto:xorg-
>bounces at] On Behalf Of James Cloos
>Sent: Tuesday, August 30, 2005 11:57 PM
>To: Discuss issues related to the xorg tree
>Subject: Re: Input device design (3)
>BTW, just to be clear, I (at least) wasn't thinking of having the
>actual i/o events go through this os-dependant, external server,
>but rather just the initial discovery and hotplugging of i/o devices.
>I was expecting the external server to notify the X server of the
>locations of the devices.  Ie, on Linux it could tell the X server
>that /dev/input/event5 just appeared, is a pointer, and should join
>the set of core pointers.  Or that eg /dev/input/event2 went away
>and should be close(2)ed.  Et cetera.
>Routing the actual input events through such an external server seems
>like too much overhead and latency, though I could easily be wrong;
>perhaps that is after all the best option for input devices, if not
>for output devices (screens, speakers, readers, braille, etc).
>Someone should test it out and see how well -- or not -- it works in
>James H. Cloos, Jr. <cloos at>
>xorg mailing list
>xorg at

More information about the xorg mailing list