From: John Silva <jps@aerizen.com>
To: David Riley <oscar@the-rileys.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac12
Date: Mon, 05 Mar 2001 13:48:26 -0800 [thread overview]
Message-ID: <3AA409AA.BD6B1631@aerizen.com> (raw)
In-Reply-To: <E14a26R-0007lp-00@the-village.bc.nu> <3AA406FC.31A212C@the-rileys.net>
I've used 82c686a at UDMA66 on MSI 694D with WD418000 and standard UDMA66 18"
cables quite successfully.
David Riley wrote:
> Alan Cox wrote:
> > 2.4.2-ac12
> > o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
> > |No UDMA66 on 82c686
>
> Um... Does that include 686a? 82c686a is supposed to handle UDMA66...
> Or is it a corruption issue again? UDMA66 seems to work fine on
> mine... No corruptions yet.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-03-05 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 21:01 Linux 2.4.2ac12 Alan Cox
2001-03-05 21:17 ` Alexander Viro
2001-03-05 22:43 ` Sergey Kubushin
2001-03-05 22:56 ` J . A . Magallon
2001-03-05 23:11 ` Alexander Viro
2001-03-06 2:06 ` Alan Cox
2001-03-06 2:39 ` Alexander Viro
2001-03-05 23:13 ` Sergey Kubushin
2001-03-05 23:30 ` J . A . Magallon
2001-03-05 23:07 ` Jeff Garzik
2001-03-05 23:21 ` Sergey Kubushin
2001-03-05 23:31 ` Jeff Garzik
2001-03-06 2:04 ` Alan Cox
2001-03-06 2:10 ` Sergey Kubushin
2001-03-06 2:19 ` Alan Cox
2001-03-05 21:37 ` David Riley
2001-03-05 21:48 ` John Silva [this message]
2001-03-06 8:14 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2001-03-05 21:01 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=3AA409AA.BD6B1631@aerizen.com \
--to=jps@aerizen.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar@the-rileys.net \
/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.