From: Matthew Wilcox <willy@linux.intel.com>
To: Theodore Tso <tytso@mit.edu>,
Robert Hancock <hancockrwd@gmail.com>,
Alex Buell <alex.buell@munted.org.uk>,
Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, Linux
Subject: Re: No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question)
Date: Fri, 1 May 2009 07:09:14 -0700 [thread overview]
Message-ID: <20090501140914.GD10704@linux.intel.com> (raw)
In-Reply-To: <20090501131459.GA7681@mit.edu>
On Fri, May 01, 2009 at 09:14:59AM -0400, Theodore Tso wrote:
> Gaah.... so basically a SATA device (the X25-M) is talking to a
> SATA-PATA bridge chip, which is then talking the IDE port in the ICH8
> chipset, which shows up as piix, which we're then pretending is SATA
> at the OS level via the ata_piix driver. Did I get that right?
> (Excuse me while I go find a barf bag....)
Well ... libata doesn't pretend that everything is SATA; it uses
taskfiles which work for both PATA and SATA. Other than that, I think
you've got it right.
> Oh.... and I suspect I know why they did it; I'm guessing they wanted
> to support PATA Ultrabay devices for backwards compatibility on the
> X60, and perhaps they were running out of connector pins on the
> docking station (the Ultrabay slot is on the X61's "media slice"), and
> they didn't have enough wires to run both PATA and SATA interfaces to
> the docking station, *and* they wanted to use the same docking station
> for the X60 and X61 Thinkpads.
>
> Ah, well. I hope it made sense to *someone* at Lenovo... It would be
> interesting to see if they fixed this in the X200 or not.
Backwards compatibility is a pain. It looks like from this lspci:
https://bugzilla.redhat.com/attachment.cgi?id=317327 that the X200 uses
ICH9M which doesn't appear to have an IDE port on the chip (document
316972-004). So it must be fixed in the X200 ... unless they've put in
a SATA-PATA bridge in the base, and a PATA-SATA bridge in the ultrabay
...
Even then, it might work. I don't know enough about the PATA protocol
to say.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@linux.intel.com>
To: Theodore Tso <tytso@mit.edu>,
Robert Hancock <hancockrwd@gmail.com>,
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 07:09:14 -0700 [thread overview]
Message-ID: <20090501140914.GD10704@linux.intel.com> (raw)
In-Reply-To: <20090501131459.GA7681@mit.edu>
On Fri, May 01, 2009 at 09:14:59AM -0400, Theodore Tso wrote:
> Gaah.... so basically a SATA device (the X25-M) is talking to a
> SATA-PATA bridge chip, which is then talking the IDE port in the ICH8
> chipset, which shows up as piix, which we're then pretending is SATA
> at the OS level via the ata_piix driver. Did I get that right?
> (Excuse me while I go find a barf bag....)
Well ... libata doesn't pretend that everything is SATA; it uses
taskfiles which work for both PATA and SATA. Other than that, I think
you've got it right.
> Oh.... and I suspect I know why they did it; I'm guessing they wanted
> to support PATA Ultrabay devices for backwards compatibility on the
> X60, and perhaps they were running out of connector pins on the
> docking station (the Ultrabay slot is on the X61's "media slice"), and
> they didn't have enough wires to run both PATA and SATA interfaces to
> the docking station, *and* they wanted to use the same docking station
> for the X60 and X61 Thinkpads.
>
> Ah, well. I hope it made sense to *someone* at Lenovo... It would be
> interesting to see if they fixed this in the X200 or not.
Backwards compatibility is a pain. It looks like from this lspci:
https://bugzilla.redhat.com/attachment.cgi?id=317327 that the X200 uses
ICH9M which doesn't appear to have an IDE port on the chip (document
316972-004). So it must be fixed in the X200 ... unless they've put in
a SATA-PATA bridge in the base, and a PATA-SATA bridge in the ultrabay
...
Even then, it might work. I don't know enough about the PATA protocol
to say.
next prev parent reply other threads:[~2009-05-01 14:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 2:07 No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question) Theodore Ts'o
2009-04-30 2:19 ` Tejun Heo
2009-04-30 2:27 ` 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 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 13:59 ` Matthew Garrett
2009-05-01 14:09 ` Matthew Wilcox [this message]
2009-05-01 14:09 ` Matthew Wilcox
2009-04-30 15:42 ` Henrique de Moraes Holschuh
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=20090501140914.GD10704@linux.intel.com \
--to=willy@linux.intel.com \
--cc=alex.buell@munted.org.uk \
--cc=hancockrwd@gmail.com \
--cc=jeff@garzik.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 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.