On Sat, Oct 26, 2002 at 09:05:38PM -0400, Zephaniah E. Hull wrote:
> To make a long story short, mousedev.c does not properly implement the
> EXPS/2 protocol, specificly dealing with the wheel.
>
> The lower 8 bits of the 4th byte are supposed to be 0x1 or 0xf to
> indicate movement of the first wheel, and 0x2 or 0xe for the second
> wheel.
Hi,
I was talking about this problem with Vojtech some months ago,
and unfortunately we were not able to find correct way to implement it:
there are mouses (probably majority) which have only one wheel, and
which reports fast wheel movement as 2,3,4... or 0xe,0xd,.... Protocol
is documented this way on Microsoft web pages.
Then there is another group of mices (mine A4Tech with two wheels
being one of them) which reports vertical wheel always as 1/0xF, and
horizontal as 2/0xE (and if you move both, they reports once horizontal
and once vertical wheel).
Unfortunately we were not able to find how to detect these mouses in
advance, and when I asked A4Tech, I got back answer that I should use
their mouse driver, and not one delivered by Microsoft (although Linux
was every third word in question). From this answer I conclude that
there is no way to autodetect it, and it has to be specified by some
options passed to mouse driver.
Petr Vandrovec
vandrove@vc.cvut.cz
-
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/
This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:36 EST