From: Matthew Wilcox <willy@linux.intel.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>,
Alex Buell <alex.buell@munted.org.uk>,
Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question)
Date: Fri, 1 May 2009 04:35:33 -0700 [thread overview]
Message-ID: <20090501113533.GB10704@linux.intel.com> (raw)
In-Reply-To: <49FA78B4.2070900@gmail.com>
On Thu, Apr 30, 2009 at 10:21:08PM -0600, Robert Hancock wrote:
> I'm suspecting that that Ultrabay slot might be using the PATA ports on
> the chipset, with a PATA-SATA bridge chip or something. I haven't seen
> an Intel chipset with some SATA ports using AHCI and some in PIIX mode
> before, the ones I've seen with both had the PIIX mode driving PATA
> ports. If it is indeed bridged through PATA on that laptop, there's no
> way you're going to get any NCQ support on that slot.
>
> I don't know why Lenovo would do that, as it would kind of cripple SATA
> drives in that slot, but hardware people do some bizarre things
> sometimes..
I have to agree with Robert. If you look at the ich8 data sheet
(313056-003), the mobile version has 3 ATA ports and 1 IDE port "that
can be electrically isolated". See pages 41, 43, and 50-51. on page 41,
it says the IDE port has "Tri-state modes to enable swap bay".
So I don't blame Lenovo for hooking up the Ultrabay slot using the IDE
port. They were pretty much told to do it.
next prev parent reply other threads:[~2009-05-01 11:35 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
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 [this message]
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=20090501113533.GB10704@linux.intel.com \
--to=willy@linux.intel.com \
--cc=alex.buell@munted.org.uk \
--cc=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).