From: Thorsten Leemhuis <fedora@leemhuis.info>
To: Chr <chunkeey@web.de>
Cc: Thorsten Leemhuis <fedora@leemhuis.info>,
Chuck Ebbert <cebbert@redhat.com>, Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Jason Gaston <jason.d.gaston@intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller
Date: Mon, 02 Jul 2007 13:44:25 +0200 [thread overview]
Message-ID: <4688E519.7040308@leemhuis.info> (raw)
In-Reply-To: <200707021324.17250.chunkeey@web.de>
On 02.07.2007 13:24, Chr wrote:
> On Monday, 2. July 2007, you wrote:
>> On 02.07.2007 07:02, Thorsten Leemhuis wrote:
>> Hmmm. From looking at the ICH8-Datasheet (
>> http://www.intel.com/design/chipsets/datashts/313056.htm
>> or http://download.intel.com/design/chipsets/datashts/31305603.pdf )
>> page 189 and later it seems to me that the ICH8M (just as all the other
>> Intel-Chipsets I know) officially only supports Ultra ATA 100 (and not
>> 133!).
>> So is the ich_pata_133 correct in the patch (see quoted line above)?
> For some strange reason, I can not get the pdf...
> Anyway, the original patch had "ich_pata_100".
> see: http://www.mail-archive.com/linux-ide%40vger.kernel.org/msg07416.html
k, missed that post.
> but Alan Cox wrote:
> http://www.mail-archive.com/linux-ide%40vger.kernel.org/msg07417.html
>> Its ich_pata_133 - all the newer chips are.
Intel afaik never supported Ultra ATA 133 officially in any of the
mainstream desktop or mobile chipsets.
>> They work even better if you
>> set them into AHCI mode in the BIOS and then they should "just work" with
>> recent kernels as the AHCI driver now matches by class.
> And "Gaston, Jason D" <jason.d.gaston@intel.com> didn't complain about it.
> it's a "bit" confusing with all "native" AHCI SATA chipset that have to emulate
> PATA for compatibility reasons...
Well, just FYI: on my Laptop AHCI is enabled and used for the SATA hard
disk. But the DVD drive still is a pata one afaics (I'm not in front of
the machine, so I can't check), connected via the pata controller -- so
for me there is no emulation involved (at least afaics).
> So, whom can we trust?
I'd trust the public datasheet in this case.
CU
thl
next prev parent reply other threads:[~2007-07-02 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 19:16 ATA: add a PCI ID for Intel Santa Rosa PATA controller Chuck Ebbert
2007-06-28 19:47 ` [patch 2.6.22-rc6] " Chuck Ebbert
2007-06-29 14:31 ` Jeff Garzik
2007-07-02 5:02 ` Thorsten Leemhuis
2007-07-02 9:07 ` Thorsten Leemhuis
2007-07-02 11:24 ` Chr
2007-07-02 11:44 ` Thorsten Leemhuis [this message]
2007-07-02 14:36 ` Chr
2007-07-04 14:03 ` Thorsten Leemhuis
2007-07-05 20:30 ` Chr
2007-07-06 19:06 ` Gaston, Jason D
2007-07-06 19:45 ` Chr
2007-07-06 20:01 ` Thorsten Leemhuis
2007-07-06 20:43 ` Jeff Garzik
2007-07-05 21:17 ` Alan Cox
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=4688E519.7040308@leemhuis.info \
--to=fedora@leemhuis.info \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=chunkeey@web.de \
--cc=jason.d.gaston@intel.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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 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).