linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	lenb@kernel.org, linux-pci@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo
Date: Mon, 28 Jun 2010 21:48:20 +0100	[thread overview]
Message-ID: <20100628204820.GA32503@srcf.ucam.org> (raw)
In-Reply-To: <4C290245.2040001@suse.cz>

On Mon, Jun 28, 2010 at 10:12:53PM +0200, Jiri Slaby wrote:
> On 06/28/2010 07:14 PM, Matthew Garrett wrote:
> > http://www-07.ibm.com/hk/products/pos/300/specs.html indicates that 
> > Windows is supported on this hardware. It would be good to verify that 
> > it also fails before we try a model-specific quirk.
> 
> It would be good for what? I don't see the point, DSDT is broken on that
> machine and the patch works this around. Why do we need testruns from
> Windows? And why you think Windows will fail anyway, they can very have
> the pretty same quirk there.

I can guarantee to you that a generic Windows install does not have a 
quirk for an IBM PoS system released years after that CD was pressed. 
The relevance is that if Windows works without a quirk, then somewhere 
our behaviour diverges from that of Windows and it's likely that other 
machines are also hit by the same issue. Users of those systems may not 
have a support contract with a commercial Linux vendor and may just 
decide to use Windows instead, so there's an incentive for us to 
determine if that's the case and fix Linux's behaviour to match Windows 
rather than to just quirk over it.

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

  reply	other threads:[~2010-06-28 20:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 21:21 [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo Jiri Slaby
2010-06-28  0:14 ` Robert Hancock
2010-06-28  6:13   ` Jiri Slaby
2010-06-28 17:14     ` Matthew Garrett
2010-06-28 20:12       ` Jiri Slaby
2010-06-28 20:48         ` Matthew Garrett [this message]
2010-06-28 21:37           ` Robert Hancock
2010-06-29 18:40             ` Jiri Slaby
2010-06-29 23:23               ` Robert Hancock
2010-06-30  9:20                 ` Jiri Slaby
2010-06-30  9:40                   ` Jiri Slaby
2010-07-06  0:28                   ` Robert Hancock
2010-07-19 16:29                     ` Jiri Slaby
2010-07-19 19:19                       ` Robert Hancock
2010-07-20  9:29                         ` Jiri Slaby
2010-08-24  8:11                           ` Jiri Slaby
2010-08-24 23:25                             ` Robert Hancock
2010-08-30  7:36                               ` Jiri Slaby
2010-09-07 11:02                                 ` Jiri Slaby
2010-09-07 14:40                                   ` Robert Hancock
2010-09-08 15:05                                     ` Jiri Slaby
2011-04-12  8:48                                       ` [RFC " Jiri Slaby
2011-04-12  8:58                                         ` Jiri Slaby
2011-04-12 15:56                                         ` Jesse Barnes
2011-04-12 15:59                                           ` Matthew Garrett
2011-04-14  9:40                                             ` Jiri Slaby
2011-05-13  7:18                                             ` Jiri Slaby

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=20100628204820.GA32503@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=hancockrwd@gmail.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jslaby@suse.cz \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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).