From: Riki Oktarianto <rkoktarianto@gmail.com>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, Mark Lord <liml@rtr.ca>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] Add quirk to set AHCI mode on ICH boards
Date: Sat, 10 Nov 2007 05:38:02 +0700 [thread overview]
Message-ID: <20071109223802.GA23004@ceren> (raw)
In-Reply-To: <4734736C.5060003@gmail.com>
On Fri, Nov 09, 2007 at 04:49:16PM +0200, Török Edwin wrote:
> There is one problem with force enabling ahci. You'll loose the CDROM on
> Dell laptops.
> Prior to force-enabling ahci there is one "device" that sees the 2 sata
> channels, and the 2 ide channels.
> When you force-enable ahci, this device becomes the ahci controller (it
> changes the device id),
> and the IDE controller will appear as a separate new device (with
> another device id), but it is disabled.
>
> There are registers on the ICH7 that allows you to set enabled/disabled
> status, but according to the documentation you should not enable a
> device after it has been disabled. In practice I couldn't get the CDROM
> to get re-enabled:
> * either nothing happend
> * spurious irqs were sent that nobody handles, unless I used irq=poll;
> but still no cdrom.
>
> Force-enabling AHCI, and not trying to enable the CDROM works, although
> I occasionally got NCQ errors.
>
> For a (long) discussion see this thread on the powertop mailing list:
> http://www.bughost.org/pipermail/power/2007-June/000533.html
> http://www.bughost.org/pipermail/power/2007-June/000573.html
>
> And there is also another slightly different approach:
> http://mjg59.livejournal.com/76062.html
>
> Best regards,
> --Edwin
>
In the MacBook, after enabling ahci the IDE controller also appeared as a
separate new device, but it is enabled and handled correctly by piix.
I haven't got any problem, even suspend/resume works fine.
Lucky us who got the ABAR mapped by the BIOS...
--
Riki Oktarianto
next prev parent reply other threads:[~2007-11-09 22:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 2:02 [PATCH] Add quirk to set AHCI mode on ICH boards Riki Oktarianto
2007-11-09 2:31 ` Jeff Garzik
2007-11-09 3:29 ` Mark Lord
2007-11-09 3:46 ` Jeff Garzik
2007-11-09 4:44 ` Mark Lord
2007-11-09 4:57 ` Jeff Garzik
2007-11-09 15:02 ` Arjan van de Ven
2007-11-09 12:04 ` Alan Cox
2007-11-09 14:49 ` Török Edwin
2007-11-09 22:38 ` Riki Oktarianto [this message]
2007-11-09 23:32 ` Matthias Schniedermeyer
2007-11-10 3:08 ` Jeff Garzik
2007-11-10 11:20 ` Matthias Schniedermeyer
2007-11-10 11:26 ` Matthias Schniedermeyer
2007-11-10 18:01 ` Mark Lord
2007-11-10 18:38 ` Matthias Schniedermeyer
2007-11-11 14:05 ` Thorsten Leemhuis
2007-11-11 18:24 ` Matthias Schniedermeyer
2007-11-10 3:05 ` Jeff Garzik
2007-11-10 3:54 ` Theodore Tso
2007-11-10 3:57 ` Jeff Garzik
2007-11-10 3:57 ` Jeff Garzik
2007-11-10 18:37 ` Allen Martin
2007-11-10 18:37 ` Allen Martin
2007-11-10 19:04 ` Jeff Garzik
2007-11-13 7:27 ` Allen Martin
2007-11-13 7:27 ` Allen Martin
2007-11-13 15:27 ` Alan Cox
2007-11-13 15:27 ` Alan Cox
2007-11-14 18:35 ` Allen Martin
2007-11-14 18:35 ` Allen Martin
2007-11-14 18:46 ` Mark Lord
2007-11-14 18:58 ` Greg KH
2007-11-09 12:45 ` Riki Oktarianto
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=20071109223802.GA23004@ceren \
--to=rkoktarianto@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=edwintorok@gmail.com \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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 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.