From: Matt Sealey <matt@genesi-usa.com>
To: Craig Block <chblock3@yahoo.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: 40-wire/80-wire detection
Date: Fri, 13 Jul 2007 01:26:45 +0100 [thread overview]
Message-ID: <4696C6C5.3070703@genesi-usa.com> (raw)
In-Reply-To: <527770.57572.qm@web58107.mail.re3.yahoo.com>
Craig Block wrote:
> Linux kernel: version 2.6.22.1
> Chipset: VIA VT8363 + VT82C686A
> Hard drives: Quantum Fireball LCT10 (UDMA66)
>
> I'm having a problem with the 80-wire/40-wire cable detection in the
> ata driver. Even when I configure the kernel with IDEDMA_IVB set, I
> still get the 40-wire speed downgrade on hda.
>
> Why did you guys put that 80-wire/40-wire cable detection in the ata
> driver anyway? Since when is it your job to police me in making sure
> I'm using the correct cable on my drives.
Since it's required by the ATA standard for anything above UDMA/33
unless the cable is ludicrously short?
> This is a pefect example of why I feel Linux isn't worth the trouble.
> If it weren't free of cost, I wouldn't go near it. But then again, I
> guess you get what you pay for so I shouldn't complain.
I think you'll find most modern BIOS implementations will nag you
incessantly if you have a UDMA/66 and beyond device with a 40-core
cable. As will most well-written Windows device drivers knock it down
but they just don't have a big, noticable warning about it (I would
never have known Intel Application Accelerator was doing it until I
looked in it's diagnostics GUI and it told me so. Turns out I had
broken my cable).
Most IDE chipsets have a register for this explicit purpose. Not
checking it would be rather negligent on the part of the driver,
not to mention if it enabled high speed operation on an unsuitable
cable you would be waving bye-bye to all your data. That's exactly
why there is no way to force it on most drivers, too.
You trade off l33t speed boosting for data integrity, you will
only lose your data faster, in the end.
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
prev parent reply other threads:[~2007-07-13 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 21:09 40-wire/80-wire detection Craig Block
2007-07-12 21:28 ` Jeff Garzik
2007-07-13 12:04 ` Stephen Clark
2007-07-13 17:58 ` Craig Block
2007-07-13 21:39 ` Bartlomiej Zolnierkiewicz
2007-07-14 8:37 ` Craig Block
2007-07-18 22:32 ` Bartlomiej Zolnierkiewicz
2007-07-24 14:47 ` Sergei Shtylyov
2007-07-29 17:30 ` Bartlomiej Zolnierkiewicz
2007-07-13 0:26 ` Matt Sealey [this message]
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=4696C6C5.3070703@genesi-usa.com \
--to=matt@genesi-usa.com \
--cc=chblock3@yahoo.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).