From: Tejun Heo <tj@kernel.org>
To: Alex Buell <alex.buell@munted.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>, Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question)
Date: Thu, 30 Apr 2009 16:45:29 +0900 [thread overview]
Message-ID: <49F95719.10701@kernel.org> (raw)
In-Reply-To: <20090430083309.437f9248@lithium.local.net>
Alex Buell wrote:
> On Wed, 29 Apr 2009 22:27:46 -0400, I waved a wand and this message
> magically appears in front of Jeff Garzik:
>
>> As Tejun noted, try switching to AHCI mode in BIOS.
>
> But is there a way to switch modes without needing to go through the
> BIOS? Some laptops won't let you do that through BIOS.
There is and it isn't too difficult either in itself but the problem
is that for ahci mode to work the ABAR (PCI BAR 5) needs to be
allocated and enabled. On x86, the kernel takes the PCI resources
allocated by BIOS. Doing it directly isn't necessarily difficult but
is too dangerous as there can be areas which aren't described anywhere
but still are used by something.
Because ICHs don't enable ABAR in piix mode unless SCRAE is set and
most BIOSen don't set SCRAE, ABAR don't get allocated nor its space
get reserved in most cases if the controller is in piix mode.
So, at the point of driver load, there just isn't much we can do about
the missing ABAR. It's sad. Dunno why some laptop manufacturers
still program the thing into piix mode. :-(
Thanks.
--
tejun
next prev parent reply other threads:[~2009-04-30 7:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LzLgA-0004j6-9W@closure.thunk.org>
2009-04-30 2:27 ` No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question) Jeff Garzik
2009-04-30 7:33 ` Alex Buell
2009-04-30 7:45 ` Tejun Heo [this message]
2009-04-30 13:47 ` Alan Cox
2009-04-30 15:35 ` Matthew Wilcox
2009-04-30 15:47 ` Matthew Garrett
2009-05-01 1:49 ` Robert Hancock
2009-05-03 2:07 ` Tejun Heo
2009-05-03 20:50 ` Robert Hancock
2009-05-03 22:35 ` Jason Riedy
2009-04-30 11:34 ` Theodore Tso
2009-04-30 11:38 ` Theodore Tso
2009-05-01 1:51 ` Robert Hancock
2009-05-01 2:51 ` Theodore Tso
2009-05-01 4:21 ` Robert Hancock
2009-05-01 11:35 ` Matthew Wilcox
2009-05-01 13:14 ` Theodore Tso
2009-05-01 13:59 ` Matthew Garrett
2009-05-01 14:09 ` Matthew Wilcox
2009-04-30 15:42 ` Henrique de Moraes Holschuh
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=49F95719.10701@kernel.org \
--to=tj@kernel.org \
--cc=alex.buell@munted.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=willy@linux.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).