nanogui@linuxhacker.org

On Tue, 5 Dec 2000, Tasnim Ahmed wrote:
> # gpm -R -t imps2

Just to clarify this, you need to run gpm in repeater mode by starting it
with the -R flag. This causes it to write mouse data in mouse-systems
format (regardless of the kind of mouse) to a fifo at /dev/gpmdata whilst
in graphics mode. There is a problem with this in that the mouse-systems
format doesn't include any wheel data, so in order to use the wheel under
X, you need to use the native X mouse driver in IMPS/2 mode. But if you're
already running gpm in repeater mode, it will also try to read /dev/psaux
when in graphics mode (at the same time as X) and the mouse data will be
corrupted. So if you use gpm in repeater mode and tell X to use
/dev/gpmdata you can't use the wheel, and if you use gpm in non repeater
mode and tell X to use /dev/psaux you can't use Nano-X in framebuffer mode
without restarting gpm. Long term, we should really write our own mouse
drivers- the gpm code is a mess anyway, plus a typical embedded system
wouldn't use it so it's a waste of resources (memory, flash or disk 
space, and processor time). We'll also need to do it to get wheel support.

-- 
------- Alex Holden -------
http://www.linuxhacker.org/
 http://www.robogeeks.org/