mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lionel Bouton <Lionel.Bouton@inet6.fr>
Cc: Andre Hedrick <andre@linux-ide.org>,
	Teodor Iacob <Teodor.Iacob@astral.kappa.ro>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: UDMA 133 on a 40 pin cable
Date: 02 Jan 2003 23:24:07 +0000	[thread overview]
Message-ID: <1041549847.24901.71.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3E14B698.8030107@inet6.fr>

On Thu, 2003-01-02 at 22:00, Lionel Bouton wrote:
> I'm wondering some things about IDE 40/80 pin cables since some time ago :
> - somehow the circuitry can make the difference between 40 and 80 pin 
> (probably some pins are shorted or not by the cables or some 
> cable-type-dependent impedance between wires is mesured) and set a bit 
> for us to use.
> - most probably the same circuitry can't verify the length of the cables 
> or their overall quality but I'm unsure.
> 
> #1 How is the 40/80 pin detection done at the hardware level ?
> #2 Are there any other cable-quality hardware tests done by the chipsets 
> ? How ?

Oh god. Andre described this one as needing a "two beer" explanation.
I'd recommend stronger drinks however.

> I've encountered a barebone design (Mocha P4, uses 2.5" drives) where 
> the IDE cable was 40-pin but :
> - has a single drive connector instead of the common two,
> - its length is only around 10 or 15 cm.
> A buyer contacted me for SiS IDE driver directions on this platform and 
> confirmed this at least for his purchase.
> 
> #3 Is the above cable electrically able to sustain 66+ UDMA transfers 
> (could I hack a driver in order to bypass the 80pin cable detection and 
> make it work properly) ?

It is possible to do this yes. Other vendors do it as well. Careful
cable choice lets you meet the electrical requirements other ways in
certain situations.




  parent reply	other threads:[~2003-01-02 22:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 18:29 Teodor Iacob
2003-01-02 19:37 ` Alan Cox
2003-01-02 18:59   ` Teodor Iacob
2003-01-02 19:21     ` Samuel Flory
2003-01-02 19:23       ` Teodor Iacob
2003-01-02 19:47         ` Samuel Flory
2003-01-02 20:37           ` Teodor Iacob
2003-01-03  2:26           ` Joshua Stewart
2003-01-02 22:00   ` Lionel Bouton
2003-01-02 22:40     ` Ross Biro
2003-01-02 22:42       ` Teodor Iacob
2003-01-03  1:04         ` Lionel Bouton
2003-01-03  1:57           ` Alan Cox
2003-01-03 10:20             ` IDE termination (was Re: UDMA 133 on a 40 pin cable) John Bradford
2003-01-03 10:29               ` Andre Hedrick
2003-01-02 23:24     ` Alan Cox [this message]
2003-01-02 22:45       ` UDMA 133 on a 40 pin cable Ross Biro
2003-01-03  1:15       ` Lionel Bouton
2003-01-03 16:14     ` 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=1041549847.24901.71.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Lionel.Bouton@inet6.fr \
    --cc=Teodor.Iacob@astral.kappa.ro \
    --cc=andre@linux-ide.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

all inboxes | Powered by JetHome®