From: Mark Lord <kernel@teksavvy.com>
To: Matthew Garrett <mjg@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Joerg Dorchain <joerg@dorchain.net>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pci maillist <linux-pci@atrey.karlin.mff.cuni.cz>
Subject: Re: [Patch] enable AHCI mode on certain ich chipsets
Date: Thu, 17 Feb 2011 17:52:32 -0500 [thread overview]
Message-ID: <4D5DA6B0.5080902@teksavvy.com> (raw)
In-Reply-To: <20110217163649.GC20662@srcf.ucam.org>
On 11-02-17 11:36 AM, Matthew Garrett wrote:
> On Wed, Feb 16, 2011 at 02:45:56PM -0500, Jeff Garzik wrote:
>
>> How is the assignment of the AHCI BAR handled? Does this happen
>> automatically because it's an early fixup?
>>
>> That is traditionally the stumbling block...
>
> Yes, because it's an early fixup the kernel should allocate it itself.
> It's small enough that I'd hope we don't have trouble finding one...
It works here (the AHCI BAR setup) with this patch,
though the workaround itself doesn't work because my
Dell machine requires extra/secret fiddling to switch
things fully over to AHCI.
The patch does seem harmless enough to include in the kernel, though.
next prev parent reply other threads:[~2011-02-17 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 9:05 [Patch] enable AHCI mode on certain ich chipsets Joerg Dorchain
2011-02-16 19:45 ` Jeff Garzik
2011-02-17 16:36 ` Matthew Garrett
2011-02-17 22:52 ` Mark Lord [this message]
2011-02-17 17:42 ` Joerg Dorchain
2011-02-17 10:03 ` Tejun Heo
2011-02-17 18:09 ` Joerg Dorchain
2011-02-18 14:03 ` Bjørn Mork
2011-02-18 14:42 ` Tejun Heo
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=4D5DA6B0.5080902@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=jeff@garzik.org \
--cc=joerg@dorchain.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mjg@redhat.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).