From: Chr <chunkeey@web.de>
To: Thorsten Leemhuis <fedora@leemhuis.info>
Cc: 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>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller
Date: Mon, 2 Jul 2007 16:36:24 +0200 [thread overview]
Message-ID: <200707021636.25192.chunkeey@web.de> (raw)
In-Reply-To: <4688E519.7040308@leemhuis.info>
On Monday, 2. July 2007, Thorsten Leemhuis wrote:
> > 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.
You're probably right! But, what about Intel's ICH5 and ICH7/7-R (i945, i975)?
see ata_piix.c: line 193ff
{ 0x8086, 0x24DB, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_133 },
[...]
{ 0x8086, 0x27DF, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_133 },
On the other hand, we can leave it, because of a "off-by-one error" in ata_piix.c,
do_pata_set_dmamode, line ~770:
(the comment is important!)
/*
* --> UDMA is handled by a combination of clock switching and
* selection of dividers <---
* [...]
*/
u_speed = min(2 - (udma & 1), udma);
if (udma == 5)
u_clock = 0x1000; /* 100Mhz */ <-- wrong! it's 133Mhz.
else if (udma > 2)
u_clock = 1; /* 66Mhz */
else
u_clock = 0; /* 33Mhz */
=>
for udma = 6(133MB/s) , we get u_speed=2 and u_clock=1
for udma = 4(66MB/s), we get the "same" values! (u_speed=2 and u_clock=1)
...
so, atleast for ata_piix, UDMA6 and UDMA4 *is* the same, right?
>
> >> 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).
>
I know. I wanted to say something else... but it doesn't really matter
(not every operating system supports AHCI-only controllers by default...)
Thanks,
Chr.
next prev parent reply other threads:[~2007-07-02 14:36 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
2007-07-02 14:36 ` Chr [this message]
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=200707021636.25192.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=fedora@leemhuis.info \
--cc=jason.d.gaston@intel.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).