From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Tony Battersby <tonyb@cybernetics.com>,
Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: AHCI problem with hotplug
Date: Fri, 02 Jan 2009 12:12:06 +0900 [thread overview]
Message-ID: <495D8606.5070807@kernel.org> (raw)
In-Reply-To: <49596D9E.3040904@kernel.org>
Hello,
Tejun Heo wrote:
> This is consistent with the BIOS tristating those ports. I don't
> remember the name of the register. I'll look it up later.
Yeah, the PCS register. From ICH8 datasheet (ICH7 datasheet doesn't
have the following paragraph but it's what the BIOS is supposed to do
all the same).
If an AHCI-aware or RAID enabled operating system is being booted
then system BIOS shall insure that all supported SATA ports are
enabled prior to passing control to the OS. Once the AHCI aware OS
is booted it becomes the enabling/disabling policy owner for the
individual SATA ports. This is accomplished by manipulating a port’s
PxSCTL and PxCMD fields. Because an AHCI or RAID aware OS will
typically not have knowledge of the PxE bits and because the PxE
bits act as master on/off switches for the ports, pre- boot software
must insure that these bits are set to ‘1’ prior to booting the OS,
regardless as to whether or not a device is currently on the port.
Can you please post the output of "lpsci -nnvvvxxx"?
--
tejun
next prev parent reply other threads:[~2009-01-02 3:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 20:32 AHCI problem with hotplug Tony Battersby
2008-12-12 16:03 ` Alan Cox
2008-12-29 8:17 ` Tejun Heo
2008-12-29 14:51 ` Tony Battersby
2008-12-29 18:29 ` Robert Hancock
2008-12-30 0:38 ` Tejun Heo
2009-01-02 3:12 ` Tejun Heo [this message]
2009-01-07 15:39 ` Tony Battersby
2009-01-08 2:06 ` Tejun Heo
2009-01-08 14:20 ` Tony Battersby
2009-01-09 0:13 ` Robert Hancock
2009-01-09 16:30 ` Tony Battersby
2009-01-14 6:33 ` Tejun Heo
2009-01-14 21:38 ` Tony Battersby
2009-01-15 1:31 ` Tejun Heo
2009-01-15 4:42 ` Robert Hancock
2009-01-20 22:56 ` Tony Battersby
2008-12-30 13:41 ` raz ben yehuda
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=495D8606.5070807@kernel.org \
--to=tj@kernel.org \
--cc=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=tonyb@cybernetics.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).