From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, greg@kroah.com, yan.i.li@intel.com
Subject: Re: [PATCH] More i8042-reset quirks for MSI Wind-clone netbooks
Date: Tue, 16 Jun 2009 18:15:49 +0100 [thread overview]
Message-ID: <20090616181549.496ae0f2@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090616164351.GA14353@srcf.ucam.org>
On Tue, 16 Jun 2009 17:43:51 +0100
Matthew Garrett <mjg59@srcf.ucam.org> 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.
Alan
next prev parent reply other threads:[~2009-06-16 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 14:16 Yan Li
2009-06-15 14:34 ` Matthew Garrett
2009-06-15 14:47 ` Li, Yan
2009-06-16 15:42 ` Matthew Garrett
2009-06-16 16:36 ` Alan Cox
2009-06-16 16:43 ` Matthew Garrett
2009-06-16 17:15 ` Alan Cox [this message]
2009-06-16 17:17 ` Matthew Garrett
2009-06-17 1:01 ` Li, Yan I
2009-06-17 2:51 ` Matthew Garrett
2009-06-18 0:08 ` Li, Yan
2009-06-18 15:42 ` Matthew Garrett
2009-06-19 7:16 ` Li, Yan I
2009-06-19 12:37 ` Matthew Garrett
2009-06-22 23:35 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090616181549.496ae0f2@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=yan.i.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®