From: Vojtech Pavlik <vojtech@suse.cz>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Tomas Szepe <szepe@pinerecords.com>,
"Gryaznova E." <grev@namesys.botik.ru>,
linux-kernel@vger.kernel.org
Subject: Re: IDE problem: linux-2.5.17
Date: Fri, 24 May 2002 00:40:57 +0200 [thread overview]
Message-ID: <20020524004057.C27005@ucw.cz> (raw)
In-Reply-To: <20020523180357.GA725@louise.pinerecords.com> <Pine.LNX.4.10.10205231143390.22581-100000@master.linux-ide.org>
On Thu, May 23, 2002 at 11:44:44AM -0700, Andre Hedrick wrote:
>
> Not true at all.
>
> Many of the OEM's use 40c's to do 66 and 100, just they have to be very
> high quality and about 6" in length.
Hmm, last time we were discussing you were saying that only 80 wire
cables work, and I was saying that short enough 40 wire cables are OK as
well (even in some older revision of the spec) ....
... interesting.
Anyway, 40 wire cables can really only work with a single drive and have
to be really short. And, Linux should only use UDMA33 and lower on
them, because it can't know the length of the cable.
>
> On Thu, 23 May 2002, Tomas Szepe wrote:
>
> > > I have 40 wires cable. When ide=nodma is passed to 2.5.17 kernel -
> > > kernel boots. Am I correct that it is not possible to have DMA
> > > on with such cable? Is there any reason for doing that?
> >
> > 40-conductor IDE cables are capable of transfering data
> > in DMA modes up to udma2, but no faster.
> >
> > T.
> > -
> > 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/
> >
>
> Andre Hedrick
> LAD Storage Consulting Group
>
> -
> 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/
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-05-23 22:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 13:58 IDE problem: linux-2.5.17 Gryaznova E.
2002-05-23 14:17 ` Martin Dalecki
2002-05-23 17:48 ` Gryaznova E.
2002-05-23 18:03 ` Tomas Szepe
2002-05-23 18:44 ` Andre Hedrick
2002-05-23 17:49 ` Martin Dalecki
2002-05-23 19:11 ` Andre Hedrick
2002-05-23 19:13 ` Andre Hedrick
2002-05-24 15:05 ` Alan Cox
2002-05-23 22:40 ` Vojtech Pavlik [this message]
2002-05-23 18:07 ` Martin Dalecki
2002-05-23 22:42 ` Vojtech Pavlik
2002-05-23 22:37 ` Vojtech Pavlik
2002-05-23 14:27 ` Martin Dalecki
2002-05-23 15:39 ` [reiserfs-dev] " Oleg Drokin
2002-05-23 14:44 ` Martin Dalecki
2002-05-23 16:00 ` Oleg Drokin
2002-05-23 22:52 ` Vojtech Pavlik
2002-05-23 21:47 ` Lionel Bouton
2002-05-23 22:55 ` Vojtech Pavlik
2002-05-24 0:23 ` Lionel Bouton
2002-05-24 1:04 ` Andre Hedrick
2002-05-24 5:56 ` Vojtech Pavlik
2002-05-24 8:53 ` Lionel Bouton
2002-05-24 4:53 ` Oleg Drokin
2002-05-23 22:50 ` Vojtech Pavlik
2002-05-24 11:03 ` Martin Dalecki
2002-05-24 13:15 ` Vojtech Pavlik
2002-05-24 12:15 ` Martin Dalecki
2002-05-24 13:20 ` Vojtech Pavlik
2002-05-24 13:40 ` Martin Dalecki
2002-05-24 14:54 ` Vojtech Pavlik
2002-05-23 15:52 ` Tomas Szepe
2002-05-23 16:02 ` Oleg Drokin
2002-05-23 22:45 ` Vojtech Pavlik
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=20020524004057.C27005@ucw.cz \
--to=vojtech@suse.cz \
--cc=andre@linux-ide.org \
--cc=grev@namesys.botik.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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