From: Robert Hancock <hancockrwd@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Seth Heasley <seth.heasley@intel.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.32.3] ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs
Date: Thu, 14 Jan 2010 18:15:56 -0600 [thread overview]
Message-ID: <51f3faa71001141615k3223a02fhb0b882b6cbe680cf@mail.gmail.com> (raw)
In-Reply-To: <20100114201136.GA3814@khazad-dum.debian.net>
On Thu, Jan 14, 2010 at 2:11 PM, Henrique de Moraes Holschuh
<hmh@hmh.eng.br> wrote:
> On Wed, 13 Jan 2010, Robert Hancock wrote:
>> Hmm, it seems like it's a bit more complicated than that. For ICH6R
>> (0x2652), ata_piix attaches to it regardless of mode intentionally, it
>> has specific logic to disable AHCI on the controller since it can be
>> used in either mode. That seems a bit questionable. Having the same
>> device being handled by different enabled drivers and depending on
>> link or module load order to decide which one loads is fragile and
>> prone to errors. I'd be in favor of removing the ICH6R support from
>> ata_piix entirely and saying that you should be using ahci for that
>> device. Maybe when ahci was immature there was a benefit to allowing
>> ata_piix to run it, but I doubt that's true today.
>
> Maybe it is the silicon AHCI in ICH6R that is immature, and one is much
> better of using it in IDE mode?
That seems unlikely, since the Intel-provided Matrix Storage drivers
for that controller on Windows will be using AHCI mode..
next prev parent reply other threads:[~2010-01-15 0:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 1:00 [PATCH 2.6.32.3] ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs Seth Heasley
2010-01-13 4:40 ` Robert Hancock
2010-01-13 11:11 ` Jeff Garzik
2010-01-13 14:59 ` David Milburn
2010-01-13 15:43 ` Heasley, Seth
2010-01-14 0:03 ` Robert Hancock
2010-01-13 15:15 ` Krzysztof Halasa
2010-01-13 17:08 ` Jeff Garzik
2010-01-13 18:18 ` Krzysztof Halasa
2010-01-13 23:57 ` Robert Hancock
2010-01-14 14:40 ` Krzysztof Halasa
2010-01-15 0:15 ` Robert Hancock
2010-01-15 21:43 ` Krzysztof Halasa
2010-01-16 1:32 ` Robert Hancock
2010-01-16 18:02 ` Krzysztof Halasa
2010-01-14 0:11 ` Robert Hancock
2010-01-14 0:42 ` Robert Hancock
2010-01-14 20:11 ` Henrique de Moraes Holschuh
2010-01-15 0:15 ` Robert Hancock [this message]
2010-01-16 3:02 ` Henrique de Moraes Holschuh
2010-01-16 4:57 ` Robert Hancock
2010-01-20 3:21 ` Tejun Heo
2010-01-14 15:40 ` Krzysztof Halasa
2010-01-20 19:28 ` Jeff Garzik
[not found] ` <201009090944.56546.seth.heasley@intel.com>
2010-09-10 23:38 ` [PATCH 2.6.35.4] ahci: AHCI and RAID mode SATA patch for Intel Patsburg DeviceIDs Seth Heasley
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=51f3faa71001141615k3223a02fhb0b882b6cbe680cf@mail.gmail.com \
--to=hancockrwd@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@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).