[ANNOUNCE] xf86-input-evdev 184.108.40.206
peter.hutterer at who-t.net
Thu Aug 13 23:46:07 PDT 2009
On Fri, Aug 14, 2009 at 09:32:13AM +0300, Maxim Levitsky wrote:
> On Fri, 2009-08-14 at 16:06 +1000, Peter Hutterer wrote:
> > On Fri, Aug 14, 2009 at 08:27:22AM +0300, Maxim Levitsky wrote:
> > > > > Folks, I have two outstanding questions about this driver.
> > > > >
> > > > > First, I have seen that XI2 input is landed in master (and I enjoy two
> > > > > mouses now :-)
> > > > >
> > > > > But, there were rumors that this will enable support for 32 bit
> > > > > keycodes, and it will be transparent, providing an updated Xlib is
> > > > > installed.
> > > > > How far we are from that?
> > > >
> > > > I doubt this will happen. Xlib itself is tightly paired with the core X
> > > > protocol which has 8 bit keycodes. Making this transparent looks simple
> > > > (Xlib itself uses ints) but would require numerous hooks within the library
> > > > to call out into new requests where possible. The devil's in the detail
> > > > here.
> > > Then, I phrase my question differently, when the X will report 32 bit
> > > keycodes to userspace via *any* interface, so toolkits can be ported?
> > > (I of course mean that events should originate from evdev)
> > XI2 for input events, already in master.
> > XKB2 for xkb configuration, not in master yet.
> But evdev still checks for keycode < 255 or whatever (247 or so)?
oops. right. this needs to be fixed, need to test this goes through the
server properly though.
More information about the xorg