ok now im totally lost.

Even if i set x and y to 0 before they get printed to mousein the
mouse still works.

I have no idea how ps/2 works, but couldn't my bios emulate it for usb devices?

So could there be two values set for mousein, one from the kernel and
one by nusb/kb and because of the ps2 emulation the kernel value is
like 3 times bigger then the negative equivalent of the userspace
driver?

Im really guessing here

-Eddi

Reply via email to