From: Tejun Heo <htejun@gmail.com>
To: Soeren Sonnenburg <sonne@nn7.de>
Cc: Matteo Croce <rootkit85@yahoo.it>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] AHCI PCI ID for MacBook Pro
Date: Sat, 10 Feb 2007 12:10:17 -0500 [thread overview]
Message-ID: <45CDFC79.1040301@gmail.com> (raw)
In-Reply-To: <1171123622.31813.9.camel@localhost>
Soeren Sonnenburg wrote:
> I don't get it. Why is it rejected then ? If I'd like to use the ahci
> mode of the ich7 r/m driver I just compile it into the kernel, else the
> piix ?!
Well, it's probably okay if you know what you want but when ich's are
present, most distributions choose to load both ahci and ata_piix while
usually preferring ahci. That should generally work. If BIOS didn't
set it up properly, ahci will fail to load then ata_piix is loaded
instead. The thing is that BIOSen are weird and it's quite possible
that switching to ahci mode might have other side effects. For one,
ACPI methods could have been written assuming certain mode and
suspend/resume might choke if the controller is put into different mode
from what BIOS has configured.
--
tejun
next prev parent reply other threads:[~2007-02-10 17:10 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
2007-02-10 16:07 ` Soeren Sonnenburg
2007-02-10 17:10 ` Tejun Heo [this message]
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=45CDFC79.1040301@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rootkit85@yahoo.it \
--cc=sonne@nn7.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.