From: Jeff Garzik <jgarzik@pobox.com>
To: Jason Papadopoulos <jasonp@boo.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-rc3 : IDE pb on Alpha
Date: Wed, 28 May 2003 21:10:54 -0400 [thread overview]
Message-ID: <3ED55E1E.90004@pobox.com> (raw)
In-Reply-To: <5.2.1.1.2.20030528203353.02367ec0@boo.net>
Jason Papadopoulos wrote:
> At 11:12 PM 5/27/03 -0400, Jeff Garzik wrote:
> >
> >FWIW, udma2 is the best you can do without accurate cable detection and
> >an 80-conductor cable.
> >
>
> Well, even with a drive capable of ATA66, an 80-pin cable, and a kernel
> configured to force assumption of higher UDMA modes, the best I've ever
> done with this stupid ALI controller is udma2. I think it's deliberately
> crippled.
"configured to force the assumption" does no good if the host controller
driver isn't detecting the cable correctly, or is not programming 80c
cable info into the host controller correctly. That's a code change not
a configuration thing.
Jeff
next prev parent reply other threads:[~2003-05-29 0:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 3:37 Linux 2.4.21-rc3 : IDE pb on Alpha Jason Papadopoulos
2003-05-27 4:53 ` Willy Tarreau
2003-05-27 9:40 ` Ivan Kokshaysky
2003-05-27 12:31 ` Willy Tarreau
2003-05-27 14:04 ` Ivan Kokshaysky
2003-05-27 14:37 ` Willy Tarreau
2003-05-28 0:38 ` Willy Tarreau
2003-05-28 1:41 ` Jason Papadopoulos
2003-05-28 3:12 ` Jeff Garzik
2003-05-29 0:35 ` Jason Papadopoulos
2003-05-29 1:10 ` Jeff Garzik [this message]
2003-05-28 14:45 ` Ivan Kokshaysky
2003-05-31 15:24 ` Ben Collins
2003-06-01 18:40 ` Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:19 Linux 2.4.21-rc3 Marcelo Tosatti
2003-05-25 17:36 ` Linux 2.4.21-rc3 : IDE pb on Alpha Willy Tarreau
2003-05-25 17:00 ` Willy Tarreau
2003-05-25 20:37 ` Mike Fedyk
2003-05-25 20:45 ` Bartlomiej Zolnierkiewicz
2003-05-25 20:55 ` Mike Fedyk
2003-05-25 21:23 ` Bartlomiej Zolnierkiewicz
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=3ED55E1E.90004@pobox.com \
--to=jgarzik@pobox.com \
--cc=jasonp@boo.net \
--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