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 ..
a little "warning" to all the mouse driver coder
a little "warning" to all the mouse driver coder
Last edited by kmtdk on Sat May 30, 2009 3:32 pm, edited 1 time in total.
well, what to say, to much to do in too little space.
when it goes up hill, increase work, when it goes straight, test yourself but when going down, slow down.
when it goes up hill, increase work, when it goes straight, test yourself but when going down, slow down.
- Brynet-Inc
- Member
- Posts: 2426
- Joined: Tue Oct 17, 2006 9:29 pm
- Libera.chat IRC: brynet
- Location: Canada
- Contact:
Re: a little "warning" to all the mouse driver coder
Did you mean encountered perhaps? that's one impressive typo.
- gravaera
- Member
- Posts: 737
- Joined: Tue Jun 02, 2009 4:35 pm
- Location: Supporting the cause: Use \tabs to indent code. NOT \x20 spaces.
Re: a little "warning" to all the mouse driver coder
Thanks. I'll be sure to at least remember that part about the ATX form factor boards returning 0xFE when no hardware is connected. That's useful stuff right there, dude.
17:56 < sortie> Paging is called paging because you need to draw it on pages in your notebook to succeed at it.