From: Peter Samuelson <peter@cadcamlab.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andre Hedrick <andre@linux-ide.org>,
Hakan Lennestal <hakanl@cdt.luth.se>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.0, test10, test11: HPT366 problem
Date: Tue, 21 Nov 2000 06:15:11 -0600 [thread overview]
Message-ID: <20001121061511.F2918@wire.cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10011210112530.26514-100000@master.linux-ide.org> <8094.974804486@redhat.com>
In-Reply-To: <8094.974804486@redhat.com>; from dwmw2@infradead.org on Tue, Nov 21, 2000 at 11:01:26AM +0000
[hakanl@cdt.luth.se]
> > Udma3 seem to be rock solid though as long as it manages to pass
> > the partition detection during boot up.
[David Woodhouse]
> If it falls over at udma3, perhaps we should blacklist it all the way
> down to udma2?
The way I understood Hakan was: "it boots in udma4, and if it gets all
the way to userland I immediately hdparm it down to udma3, and then it
works fine".
Hakan, is this what you meant? If so, forcing it <= udma3 should be ok.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-21 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 7:39 Hakan Lennestal
2000-11-21 9:29 ` Andre Hedrick
2000-11-21 11:01 ` David Woodhouse
2000-11-21 12:15 ` Peter Samuelson [this message]
2000-11-21 12:26 ` Hakan Lennestal
2000-11-21 13:29 ` David Woodhouse
2000-11-21 18:33 ` Andre Hedrick
2000-11-21 20:56 ` David Woodhouse
2000-11-21 21:04 ` Mohammad A. Haque
2000-11-21 21:37 ` Hakan Lennestal
2000-11-24 20:46 ` Nathan A. Ferch
2000-11-21 18:32 ` Andre Hedrick
2000-11-21 19:15 ` David Woodhouse
2000-11-22 1:11 ` Andre Hedrick
2000-11-21 10:35 ` David Woodhouse
2000-11-21 10:52 ` Hakan Lennestal
2000-11-21 9:31 Hakan.Lennestal
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=20001121061511.F2918@wire.cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=andre@linux-ide.org \
--cc=dwmw2@infradead.org \
--cc=hakanl@cdt.luth.se \
--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
all inboxes | Powered by JetHome®