public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <rossb@google.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lionel Bouton <Lionel.Bouton@inet6.fr>,
	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:45:34 -0800	[thread overview]
Message-ID: <3E14C10E.3060702@google.com> (raw)
In-Reply-To: 1041549847.24901.71.camel@irongate.swansea.linux.org.uk

>
>
>>#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.
>
>
>  
>
on the kernel command line ide0=ATA66 bypasses the check for ide channel 0.

    Ross




  reply	other threads:[~2003-01-02 22:38 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
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 [this message]
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=3E14C10E.3060702@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