Re: X11R7.0

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

On Sestdiena, 28. Janv=E2ris 2006 04:11, Zephaniah E. Hull wrote:
> On Fri, Jan 27, 2006 at 09:32:20AM +0200, Aivils Stoss wrote:
> > On Ceturtdiena, 26. Janv=E2ris 2006 23:09, Peter Schrammel wrote:
> > > Yop, that seems to work. I'm useing
> > > setxkbmap de -keycodes 'xfree86+aliases(qwertz)+aliases(evdev)' -opti=
on
> > >
> > > but my up/down keys are a mess. Pressing them sometimes causes a 100%
> > > CPU load (Xorg and kwin). But this happens only on console :0 with a
> > > ps/2 keyboard and only with the extra cursor keys (not those on the
> > > numpad).
> > >
> > > On console :2 (usb) it runs smoothly, everything's fine.
> > >
> > > Tell me if I can provide you with some debug info.
> > >
> > > Sorry, avilis. I don't have a X build system installed here and (if
> > > debian helps me) never will so I can't test the patches. But thanks
> > > anyway.
> >
> > If You are not fanatic compile-from-scratch sympatizer, then You can try
> > out this one:
> > http://www.ltn.lv/~aivils/files/evdev-zeh-060127.tar.bz2
> >
> > Must have X server sources. Edit SERVER_SRC line in the Makefile
> >
> > Aivils
>
> Thanks a ton for putting that together.
>
> However there's been a slight bug fix patch update which helps
> compiling with some compilers.
>
> If you'd like I can generate a diff between that version and current?

I download new version. It contains old bug: EvdevReadInput() may
call EvdevRelSyn() on EV_SYN, but for keyboards relative stuff is=20
uninitialised - segfault. Of course driver must be capable hadle
keys and axis events together from tablet devices, which have keys,
absolute and relative axis and buttons too.

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

Aivils