On Tue, Jun 16, 2009 at 06:15:49PM +0100, Alan Cox wrote: > On Tue, 16 Jun 2009 17:43:51 +0100 > Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: > > > On Tue, Jun 16, 2009 at 05:36:18PM +0100, Alan Cox wrote: > > > > So? If the alternative is machines that don't work until they're added > > > > to a blacklist, then the correct thing to do is to do it > > > > unconditionally. > > > > > > I would disagree: that breaks a whole pile of other machines > > > > I was under the impression that this was the reset path that Windows > > followed. If not then that suggests that we're fixing it wrong in the > > first place? > > You need to magically divine what various random windows driver > patches do and also allow for the fact that your i8042 may be completely > faked SMM, partially faked, or just randomly confused. Resetting loses > various bits of config/status that get put back by windows drivers we > don't have enough info on and in machine specific ways. So the touchpad on these machines doesn't work with generic Windows? I'm interested in the specifics, not general issues with i8042 implementations. We've repeatedly seen that these quirk tables end up inadequately comprehensive and in several cases have masked the actual problem. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
