Re: [PATCH 0/8] New set of input patches

[Pavel Machek]

Hi!

> > > 03-i8042-broken-mux-workaround.patch
> > > 	- Some MUXes get confused what AUX port the byte came from. Assume
> > > 	  that is came from the same port previous byte came from if it
> > > 	  arrived within HZ/10
> > 
> > Does that mean that (even if my hw is ok) when I two mice at once
> > I get random movements?
> 
> No, that code will only kick in if your MUX gets confused and not during
> normal course of operation. Some MUXes, when confused, raise MUXERR flag
> but leave the data byte intact in violation of active multiplexing spec.
> which says that with MUXERR the only valid data bytes are 0xfd, oxfe and
> 0xff (to signal timeout, resend or parity error). So if we get something
> other than 0xfd, 0xfe or 0xff within HZ/10 of last successfully transmitted
> byte we assume that MUX got confused and the byte was sent by the same
> device that transmitted the previous byte.
> 
> Does it make any sense?

Yes... Hmm, it is wonderfull in how many ways hardware can be
broken...

								Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/