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 :-/
> > Something that occurred to me, and I could be totally wrong here, but
> > is it possible that the trackball is being detected as a "generic
> > mouse" when it isn't one?
>
> Most likely (95%) it behaves a generic ps/2 mouse. After all, it seems
> to send generic ps/2 data. Why the data isn't getting through, is the
> question.
>
> > I tried connecting the generic mouse, disconnecting it, and then
> > connecting the trackball, and saw in dmesg that some kind of handshake
> > was going on. This was completely different for mouse and trackball.
> > Would it be any use to post this output?
>
> If it was different, then definitely!
Sorry, I was wrong, I think I pressed a mouse button whilst connecting it and mis-read the info. The init is exactly the same.
However, the data sent from each one seems to be very different, (I've re-formatted this a bit to save space, but it's from the dmesg output):
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
> > If the evbug module is the only way to go, I'll try it, but it'll
> > probably take me the rest of the day, (seriously) :-).
>
> Let's try other ways before that.
Good idea :-)
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/