linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: yan.i.li@intel.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>a
Subject: Re: [PATCH] More i8042-reset quirks for MSI Wind-clone netbooks
Date: Thu, 18 Jun 2009 16:42:50 +0100	[thread overview]
Message-ID: <20090618154250.GA30209@srcf.ucam.org> (raw)
In-Reply-To: <20090618000809.GB16835@thyme.bj.intel.com>

On Thu, Jun 18, 2009 at 08:08:09AM +0800, Li, Yan wrote:
> On Wed, Jun 17, 2009 at 03:51:01AM +0100, Matthew Garrett wrote:
> > On Wed, Jun 17, 2009 at 09:01:40AM +0800, Li, Yan I wrote:
> > > This seems a change too aggressive for me. Do we have a good reason
> > > for taking this risk? 
> > 
> > It's generally much easier to find regressions (people complain) than it 
> > is to find things that have never worked (people just assume Linux is 
> > broken).
> 
> That's true. But we are not sure how many regressions we'll meet and
> whether the efforts devoted to handle them is worthy. (How to handle
> regressions? Perhaps, ironically, we'll need another 'whitelist' for
> them!)

If we hit regressions then it's the wrong fix and would have to be 
reverted. Better a small blacklist than a large whitelist (though, in 
the general case, the presence of either is an indication of a bug)

> > > Of course if we found the "actual problem" we'd conjure up a better 
> > > fix. But before that, I'd prefer the conservative way.
> > 
> > Does stock Windows work on the machine? I think this really ought to be 
> > a pretty obvious minimal test before adding quirks to the kernel.
> 
> Does this matter?  Does whether Windows fail or not affect our
> decision here?  (Worse that I have no "stock Windows XP" for
> testing. All I have are those companion Windows Recovery CDs that
> include all drivers).

Yes. If Windows works without hardware specific drivers then there's a 
flaw in our i8042 setup code that's affecting an unknown number of 
machines, and adding more entries to a static table tells us nothing 
about what proportion of those machines are now fixed - it just tells us 
that we've worked around the issue for the ones that Intel happen to be 
testing.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-06-18 15:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 14:16 [PATCH] More i8042-reset quirks for MSI Wind-clone netbooks 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
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 [this message]
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=20090618154250.GA30209@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).