a little "warning" to all the mouse driver coder
Posted: Sat May 30, 2009 1:51 pm
well
since i have encountered some few different things with my own mouse [ on different systems], i can tell you some few things to be aware of:
laptops :
the synspad [touchpad] is normaly ought to act like a normal ps2 device, but you will have to be aware with the "read command byte" from the controller, since it takes SOME time to reach. in my example, when i send the mouse a command, this "trash" from the read command byte, kills the command.
newer computer (bios / motherboards):
when a ps2 is not connected it just sends "FE" (at least one of my computers does this), and countinues with this, until you plug in a ps2 mouse.
older computers:
works good
but if you suddently connect a mouse without have done that at POST (bios boot) it cannot find the mouse ! .
KMT dk
edit 2:
spell error corrected ..
since i have encountered some few different things with my own mouse [ on different systems], i can tell you some few things to be aware of:
laptops :
the synspad [touchpad] is normaly ought to act like a normal ps2 device, but you will have to be aware with the "read command byte" from the controller, since it takes SOME time to reach. in my example, when i send the mouse a command, this "trash" from the read command byte, kills the command.
newer computer (bios / motherboards):
when a ps2 is not connected it just sends "FE" (at least one of my computers does this), and countinues with this, until you plug in a ps2 mouse.
older computers:
works good
but if you suddently connect a mouse without have done that at POST (bios boot) it cannot find the mouse ! .
KMT dk
edit 2:
spell error corrected ..