> > I didn't, but I've compiled a new kernel with it in. Unfortunately,
> > it doesn't seem to do anything useful :-(.
> >
> > cat /dev/input/eventX | hexdump
> >
> > returns nothing, not even for keyboard events, which makes me think
> > I've gone wrong somewhere :-/
>
> Have you tried all of them (0, 1, 2 ...)? Btw, you can compile evbug in
> also.
Whoops, me being silly again, I actually created a single device node
called /dev/input/eventX instead of event1, event2, etc. :-)
> > mouse
> >
> > Left button - 09 00 00 08 00 00
> > Right button - 0a 00 00 08 00 00
> >
> > trackball
> >
> > Left button - 01 00 00 00 00 00
> > Right button - 02 00 00 00 00 00
>
> Hmm, interesting ... let's see what that means ...
>
> Indeed the 0x08 byte indicates the beginning of a packet. The driver
> synchronizes on that, and when it's missing, it ignores the packets.
> Thus, it ignores all the packets from the trackball.
>
> This patch should fix that:
It does. Cool!
GPM and X work perfectly.
Cheers!
John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/