[ltp] Kernel 2.6 and two mice

[James Hawtin]

On Tue, May 25, 2004 at 10:29:29PM +0200, Edi Weitz wrote:
> 1. If I do
> 
>    where I really issue a new 'cat' command /after/ I've re-plugged
>    the mouse, 'cat' should pick up the /new/ device /dev/input/mouse1
>    and show something if I move the mouse, shouldn't it? I don't
>    expect the first 'cat' to show anything because it's still
>    observing the 'old' device (so to say), but a newly started 'cat'
>    should see something, I think.
> 

That sounds about right.


> 2. If I have to live with the fact that I can only use /dev/input/mice
>    how can I achieve the behaviour that I previously had? (See the
>    email that started this thread.) This worked with kernel 2.4
>    because /dev/input/mice only bundled the USB mice but now the PS/2
>    mouse also goes through the 'unified' device. Does that mean I
>    can't have both - separate configurations for two different mouse
>    types /and/ the ability to hotplug? Looks like 2.6 is a step
>    backwards in this regard... :(
> 

It might look like that... however I have been having a poke arround in the
2.6 source (hence taking a while to reply) and it looks like if you remove 
CONFIG_INPUT_MOUSEDEV_PSAUX from your .config input will be built without ps2 
support (just like 2.4), can't seem to work out how to do this in make
menuconfig. This will change the code in drivers/input/mousedev.c changing
that would be the other way to comment it out!

James