Peter Wainwright writes:
>
> I put some debugging spew in the XFree86 mouse driver and watched
> it run; the problem seems to be with the timing of the "reset"
> sequence. This as far as I could tell is what happens:
>
> The driver seems to be sending the reset "FF", waiting for
> a while, decides there is to be no response, sends another
> reset "FF" (these are the hexadecimal representations of the bytes
> on the wire). Meanwhile the touchpad is working away... It
> sends an ACK(nowledgement) for the first reset ("FA"), and one for
> the second. So the driver receives "FA FA" where it should receive
> just the one "FA" followed by the data "AA 00". It then tries
> yet another reset... I have the synaptics interface documentation which
> is probably available somewhere on their website. It may be helpful
> in fixing this - if it needs to be fixed - it specifies the PS/2
> protocol and this reset sequence in detail including timing.
>
> I just tried again... With my original kernel (Red Hat, 2.4.20-6),
> there is a long wait on startup. With my recompiled kernel, everything
> works! Maybe this is something to try.
>
Well, I could add some code that eats up uexpected 0xFA. This may
however degrade consistency checking at other places. Increasing
the wait period for the device reply may make mouse failure
detection mainfully long.
Egbert.
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
