All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Craig Block <chblock3@yahoo.com>
Cc: Stephen.Clark@seclark.us, Jeff Garzik <jeff@garzik.org>,
	Matt Sealey <matt@genesi-usa.com>,
	linux-ide@vger.kernel.org
Subject: Re: 40-wire/80-wire detection
Date: Fri, 13 Jul 2007 23:39:42 +0200	[thread overview]
Message-ID: <200707132339.42299.bzolnier@gmail.com> (raw)
In-Reply-To: <166657.81677.qm@web58101.mail.re3.yahoo.com>


Hi,

On Friday 13 July 2007, Craig Block wrote:
> > >>Craig Block wrote:
> > >>
> > >>I'm having a problem with the 80-wire/40-wire cable detection
> 
> > Jeff Garzik wrote:
> > >
> > >If you signal a 40-wire cable too fast, you get trouble with a
> > >capital T.
> 
> Thanks everyone for graciously replying to my negative email.  I was
> pretty irritated when I found I could not disable the downgrade.  
> 
> That's fine if the driver nags about the cable, but it should up to the
> user to deal with it.  And, like any nag, it should be possible to shut
> if off.

"idex=ata66" parameter used to only override host side cable detection
but to be able to deal with short 40-wire cables it now also overrides
device side cable detection (patches were merged in Linus' tree,
2.6.23-rc1 will have them).

> As it stands, I will have to run these drives at ATA33.  My only
> recourse is to hack the driver and disable the check.  With *me*
> hacking on the code, I really run the risk of damaging my data.
> 
> Patches anyone?

Please send the output of hdparm --Istdout for this drive.

"idex=ata66" or CONFIG_IDEDMA_IVB=y should also help but we really would
like to detect and workaround such issues automatically, without the need
for user headaches. ;)

Thanks,
Bart

  reply	other threads:[~2007-07-13 21:31 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 [this message]
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

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=200707132339.42299.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=Stephen.Clark@seclark.us \
    --cc=chblock3@yahoo.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=matt@genesi-usa.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.