public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH[RFC] Quirk macbook pro 6,2 into ahci mode
Date: Mon, 19 Jul 2010 16:58:11 +0100	[thread overview]
Message-ID: <20100719155811.GA18754@srcf.ucam.org> (raw)
In-Reply-To: <4C4383D9.3060705@pobox.com>

On Sun, Jul 18, 2010 at 06:44:41PM -0400, Jeff Garzik wrote:

> I would have quirked AHCI/piix hardware into AHCI mode long ago, if  
> firmwares defaulting to piix mode would actually program the PCI BAR  
> correctly.

If you perform the fixup early enough then the PCI resource allocation 
code should take a decent stab at it. I'd feel more comfortable with 
that once we start using ACPI _CRS by default, since that gives us a 
much better chance of avoiding conflicting with some bit of motherboard 
hardware.

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

      parent reply	other threads:[~2010-07-19 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-18 16:03 [PATCH[RFC] Quirk macbook pro 6,2 into ahci mode Jens Axboe
2010-07-18 18:42 ` Matthew Garrett
2010-07-18 20:34   ` Jens Axboe
2010-07-18 21:32     ` Tino Keitel
2010-07-19  5:40     ` Tino Keitel
2010-07-19 15:49       ` Jens Axboe
2010-07-19 15:53         ` Tino Keitel
2010-07-19 15:55           ` Jens Axboe
2010-07-19 17:23             ` Mike Snitzer
2010-07-19 20:40               ` Jens Axboe
2010-07-18 22:44   ` Jeff Garzik
2010-07-19  0:25     ` Jens Axboe
2010-07-19 10:13       ` Tejun Heo
2010-07-19 15:58     ` Matthew Garrett [this message]

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=20100719155811.GA18754@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=jaxboe@fusionio.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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