public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <rossb@google.com>
To: Lionel Bouton <Lionel.Bouton@inet6.fr>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	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: Thu, 02 Jan 2003 14:40:20 -0800	[thread overview]
Message-ID: <3E14BFD4.7000909@google.com> (raw)
In-Reply-To: 3E14B698.8030107@inet6.fr

>
> #1 How is the 40/80 pin detection done at the hardware level ?


On the motherboard end of the 80 conductor cable, the connector shorts 
one of the pins to ground (maybe pin 38).  The ide controller  just 
checks to see if the pin is pulled low or not.  Pulled low = 80 pin. 
 That's one of the reasons it's important to plug IDE cables in the 
correct way.

    Ross



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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 18:29 UDMA 133 on a 40 pin cable 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 [this message]
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     ` UDMA 133 on a 40 pin cable Alan Cox
2003-01-02 22:45       ` 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=3E14BFD4.7000909@google.com \
    --to=rossb@google.com \
    --cc=Lionel.Bouton@inet6.fr \
    --cc=Teodor.Iacob@astral.kappa.ro \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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