Vojtech Pavlik wrote:> On Wed, Aug 04, 2004 at 07:38:55AM -0500, Dmitry Torokhov wrote:> > On Wednesday 04 August 2004 02:18 am, Vojtech Pavlik wrote:> > > On Wed, Aug 04, 2004 at 12:25:19AM -0500, Dmitry Torokhov wrote:> > >> > > > On Tuesday 03 August 2004 11:29 pm, Marko Macek wrote:> > > > > Jesper Juhl wrote:> > > > >> > > > > > <>I also had problems with my KVM switch and mouse when I> initially> > > > > > moved to> > > > > > 2.6, but adding this kernel boot parameter fixed it, meybe it> will help> > > > > > you as well : psmouse.proto=imps> > > > >> > > > > This doesn't help. Only the patch I sent helps me. The problem is> that the> > > > > even with psmouse.proto=imps or exps, the driver still probes for> > > > > synaptics which I> > > > > consider a bug.> > > > >> > > >> > > > No it is not - Synaptics with a track-point on a passthrough port> will have> > > > track-point disabled if it is not reset after probing for imps/exps.> > >> > > Hmm, does the imps/exps probe succeed in this case?> >> > No, it does not, at least not mine. It either does bare PS/2 or native,> but> > there are other Synaptics touchpads that can also do imps.> > Ok, so how about issuing a reset when the imps probe fails? That'd take> care of all the cases, and I suppose a Synaptics pad that can do imps> will not be confused by it.>

Synaptics requires full reset, reset-disable alone is not enough.Plus, when synaptics is detected but left in emulation mode, thedriver does synaptics-specific reset which initializes stuff thatsurvives reset-disable (for example it enables gestures so tappingis guaranteed to work).

Additionally I think it's a good idea to detect hardware regardlessof the protocol it is using so user can see what he has.

Anyway, I think that explicitely calling reset-disable after eachfailed probe is a good idea... or maybe not after each probe but justonce, before probing for generic protocols (imps/exps), like in theattached patch.