I tried to hack in USB mouse support to the FBCON driver by adding a few
lines to basically duplicate the PS/2 code, except that it opens
’/dev/usbmouse0’ instead of ‘/dev/psaux’.
It works, but not really. The mouse jumps all over the place. I thought
the current code (I’m using the stack from 2.3.28) implemented a USB
mouse using the PS/2 protocol. Does anyone know any more about this? I’m
going to try with a different mouse a bit later and see if I get
different results. FWIW, both X and gpm work fine using the 'IMPS/2’
protocol with this mouse (Razer Boomslang 2000).
I tried to hack in USB mouse support to the FBCON driver by adding a few
lines to basically duplicate the PS/2 code, except that it opens
’/dev/usbmouse0’ instead of ‘/dev/psaux’.
It works, but not really. The mouse jumps all over the place. I thought
the current code (I’m using the stack from 2.3.28) implemented a USB
mouse using the PS/2 protocol. Does anyone know any more about this? I’m
going to try with a different mouse a bit later and see if I get
different results. FWIW, both X and gpm work fine using the 'IMPS/2’
protocol with this mouse (Razer Boomslang 2000).
I’m guessing that the IMPS/2 protocol is different from the PS/2 protocol.
I tried to hack in USB mouse support to the FBCON driver by adding a few
lines to basically duplicate the PS/2 code, except that it opens
’/dev/usbmouse0’ instead of ‘/dev/psaux’.
It works, but not really. The mouse jumps all over the place. I thought
the current code (I’m using the stack from 2.3.28) implemented a USB
mouse using the PS/2 protocol. Does anyone know any more about this? I’m
going to try with a different mouse a bit later and see if I get
different results. FWIW, both X and gpm work fine using the 'IMPS/2’
protocol with this mouse (Razer Boomslang 2000).
Many thanks in advance.
The latest CVS snapshot now contains GPM mouse support.
Run gpm with the -R command line option, and you will be able to use the
framebuffer console driver with your mouse.