From: Tejun Heo <htejun@gmail.com>
To: Matteo Croce <rootkit85@yahoo.it>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] AHCI PCI ID for MacBook Pro
Date: Sat, 10 Feb 2007 09:03:55 -0500 [thread overview]
Message-ID: <45CDD0CB.2070608@gmail.com> (raw)
In-Reply-To: <200702091839.52316.rootkit85@yahoo.it>
Matteo Croce wrote:
> On Friday 09 February 2007 15:54:53 you wrote:
>> On Fri, 2007-02-09 at 15:27 +0100, Matteo Croce wrote:
>>> + { PCI_VDEVICE(INTEL, 0x27c4), board_ahci }, /* ICH7M */
>> Wasn't this PCI ID proposed for addition a while ago, and subsequently
>> rejected? Or am I missing something?
>
> rejected? why?
Ah... right.
All ICH7 R/M silicons can be put into either IDE or AHCI mode. Which
mode is used is currently determined by BIOS. If BIOS puts the
controller into ahci mode on boot, ahci is attached; otherwise,
ata_piix. This sometimes reduces confusion level but more importantly
in some cases it's not possible to use the other mode because PCI
resource allocation is upto BIOS and it's not guaranteed to allocate all
the needed resources for the mode not in use.
Till now, the policy to follow BIOS setting has worked well enough.
Most desktop BIOSen give choice between the two modes anyway. There
have been some cases where some desktops and many notebooks where the
silicon itself is capable of ahci but BIOS doesn't allow it. It seems
Mac is one of them.
--
tejun
next prev parent reply other threads:[~2007-02-10 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 17:33 [PATCH] AHCI PCI ID for MacBook Pro Root Kit
2007-02-09 9:33 ` Tejun Heo
2007-02-09 14:27 ` Matteo Croce
2007-02-09 14:54 ` David M. Lloyd
2007-02-09 17:39 ` Matteo Croce
2007-02-09 18:15 ` David M. Lloyd
2007-02-09 18:51 ` Matteo Croce
2007-02-10 10:22 ` Soeren Sonnenburg
2007-02-10 14:03 ` Tejun Heo [this message]
2007-02-10 16:07 ` Soeren Sonnenburg
2007-02-10 17:10 ` Tejun Heo
2007-02-11 15:40 ` David M. Lloyd
2007-02-09 15:45 ` Soeren Sonnenburg
2007-02-09 17:41 ` Matteo Croce
2007-02-10 10:19 ` Soeren Sonnenburg
2007-02-10 13:17 ` Tejun Heo
2007-02-10 16:03 ` Soeren Sonnenburg
2007-02-10 17:17 ` 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=45CDD0CB.2070608@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rootkit85@yahoo.it \
/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).