[Xgl/Xegl] Input Devices

Waldo Bastian bastian at kde.org
Wed Jul 27 09:13:13 PDT 2005


On Wednesday 27 July 2005 12:08, Ely Levy wrote:
> > 2) Use HAL over other hardware detection mechanisms?
> > 	Advantages:
> > 	Disadvantages:
>
> While hal is pretty standard on linux machines I'm not aware of any other
> OS which hal is fully functional on.
> If we can make it work on all OS I think its best advantage would be the
> fact that X wont need to have hardware detection code.
> Anyhow I think still someone else would need to be done for handheld
> devices as probebly they don't run hal:)

I imagine that without hal you would fall back to a static configuration file.

> > 3) Use EVDEV as primary input driver interface? My preliminary research
> > of EVDEV leads me to believe this is a powerful and useful mechanism.
> > 	Advantages:
> > 	Disadvantages:
>
> Linux specific, depends on kernel guys, I'm also not sure how debugged it
> is.But is very powerfull and nice interface.
>
> > 4) Which legacy input drivers and device types do we want to support?
> > 	Details:
>
> It would be nice to get the functionality of the synaptics driver (which
> is GPLed and there for can't be used by other X drivers or enter the X
> release).
>
> > 5) How do device settings (mouse acceleration) get set as devices are
> > added, replaced, and when switching users (Virtual Terminals)?
> > 	Possible strategies:
> >
> >
> > 6) [Add your own here]
>
> I'm not sure where it should go on your list but there are two topics I
> think need to be attended:
>
> First is where the configuration should sit. I think xhotplug should
> elimate the need for the input device section almost completly.
> I think per user configuration should be kept in some Xresource file by
> the user. (Things like mouse speed acceleration tapping and so on).
> There is however the problem of supporting 2 Xservers on the same computer
> I saw that initial support was added to next release it would be an
> intersting problem to decide which X should take over the new device
> entered.

If the Xservers run on different VTs they should both get the new device and 
do EVIOCGRAB on DEVICE_ON/DEVICE_OFF. (See 
https://bugs.freedesktop.org/show_bug.cgi?id=968#c23 )

> Maybe one should be primary and one secondary? it would also be 
> nice if the servers could communicate enough to allow passing of devices
> between them (Yea I know few security problems there).

Assuming that there is a configuration client (see 
http://wiki.x.org/wiki/XHotplugProposal ) the configuration client can decide 
which X server gets the device. 

Cheers,
Waldo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20050727/9fd8a83b/attachment.pgp>


More information about the xorg mailing list