Re: X11R7.0

[Aivils S. <ai...@un...>]

On Otrdiena, 31. Janv=E2ris 2006 22:19, Zephaniah E. Hull wrote:
> > Also one version before latest will not work proper if i create/delete
> > devices in the runtime. It is not official but i provide this one:
> > http://www.ltn.lv/~aivils/files/xentity-0.01.tar.bz2
> > This package contains xmodule, which allow load/remove X server
> > modules and xdevice, which allow create/delete X server input devices
> > at runtime. Existing input drivers are compatible with xdevice,
> > but Your not. Even xdevice never goes into main it make life easy
> > during development. You don't need server restart on new driver
> > version or on device parameter change. Fatal errors still are fatal.
> > Syntaxis like this:
> > # xmodule -l evdev
> > # xdevice -c e1,evdev,Phys,isa0060/serio0/input0,AlwaysCore,1
> > You driver changes device indentifier unwarranted. You must search new
> > device
> > # xsetpointer -l
> > normal device delete uses same identifier
> > # xdevice -d e1
>
> That looks handy, however due to hotplug support my driver is going to
> cause, interesting issues.
>
> Mainly, we create new driver instances for additional devices that are
> plugged in that match the specification for current devices.
>
> Because we need the new entries to be uniquely identifiable, we append
> the phys to the name.
>
> At this time there is no way around this.
>
> Also at the moment I'm not using a modular tree, which makes using that
> a bit harder even for testing purposes.

That package didn't use compile form scratch. All what You need is X server
source for headers, runing X binary for some variables, gcc, X server resta=
rt
is necessary. I use it under my 6.8.2.

xdevice was developed keeping in mind buch of all input devices. It does
"hotplug" in large-scale without touching driver source.
Seems SIGHUP is sacred. Even aiptek tablet developers did not replay.
=46rom my point of view looks very stupid - plug new input device and then
restart X for new config.

Aivils