Re: imps2 mouse driver and bug 2082

[Mauro Mozzarelli <mauro@ezplanet.net>]

Dmitry,

I reckon that the reconnection should be automatic, with the kernel
driver being able to detect a sync loss. I understand that the patch you
originally posted might not be ideal, however I have been using it
successfully for months now (modified for 2.6.9 and 2.6.10) and I have
included it in the standard kernel distributed with EzPlanet One.

Although we may not want to include this patch as it is, I would
consider the prioritization of this issue to be resolved in future
kernel releases.

Mauro

On Sun, 2005-03-27 at 23:21 -0500, Dmitry Torokhov wrote:
> Hi,
> 
> On Sunday 27 March 2005 18:37, Mauro Mozzarelli wrote:
> > The mouse driver, re-developed for kernel 2.6, ever since the earliest
> > 2.6 release lost the ability to reset a broken link with an IMPS2 mouse
> > (this happens when disconnecting the mouse plug either physically or
> > through a "non imps2" KVM switch). The result is that the mouse can no
> > longer be controlled, with the only solution being a RE-BOOT!
> >
> 
> You can re-initialize mouse with the following command (while mouse is
> connected):
> 
>         echo -n "reconnect" > /sys/bus/serio/devices/serioX/drvctl
> 
> where serioX is serio port your mouse is connected to. You can find out
> which one by examining the driver link:
> 



 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/