All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Tejun Heo <htejun@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: l.genoni@oltrelinux.com
Subject: Re: something strange in libata-core.c for kernel 2.6.22-rc3
Date: Sun, 20 May 2007 16:27:42 -0600	[thread overview]
Message-ID: <4650CB5E.3010603@shaw.ca> (raw)
In-Reply-To: <fa.Ldjy2OubeKomZD0OV2gRm/wpUFo@ifi.uio.no>

Tejun Heo wrote:
> l.genoni@oltrelinux.com wrote:
>> Mybe I am wrong, but if you are detecting 40-wire cable to set them to
>> DMA/33, why the check includes also 80-wire cables configuring them to
>> DMA/33 too?
>>
>> With this patch my nvidia4 IDE controllers detects correctly and
>> configure correctly DMA/100 for my HD and DMA/33 for my DVD (the first
>> uses a 80-wire cable, the second a 40-wire cable).
>>
>> Am I wrong somewhere?
> 
> That's the drive side verification of 80c cable check, so if the
> condition triggers we downgrade 80c or unknown to 40c.  Cable detection
> on nvidia PATA is a disaster.  You're supposed to do some ACPI dancing
> and drive side detection is completely bogus.  Eeeek....
> 
> Alan, did you have a chance to test the ACPI cable detection?  It just
> didn't work when I tried it.  It always returned 80c on my machine.

Hopefully when we get that support in and working it will solve a lot of 
these issues (and others, like the laptops that have a short 40-wire 
cable that is good for high UDMA speeds which we presently have to 
hard-code detection for specific models).

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


  parent reply	other threads:[~2007-05-20 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.MCe9nCgx+WnsHp+weZyM9LiDF0s@ifi.uio.no>
     [not found] ` <fa.rv8/6n3uBnAIoUHHNUW3eR7cJd8@ifi.uio.no>
     [not found]   ` <fa.LXy58QwLlPXDhsfVUU9kEfA3QbI@ifi.uio.no>
2007-05-20 17:18     ` something strange in libata-core.c for kernel 2.6.22-rc3 Robert Hancock
     [not found]     ` <fa.Ldjy2OubeKomZD0OV2gRm/wpUFo@ifi.uio.no>
2007-05-20 22:27       ` Robert Hancock [this message]
2007-05-21  8:34       ` Robert Hancock
2007-05-21  9:09         ` Tejun Heo
2007-05-21 11:15           ` Alan Cox
2007-05-21 18:14             ` Robert Hancock
2007-05-21  9:41         ` Jeff Garzik
     [not found] <Pine.LNX.4.64.0704181704270.1663@Phoenix.oltrelinux.com>
     [not found] ` <20070418162525.423b2e7e@the-village.bc.nu>
2007-05-20 12:40   ` l.genoni
2007-05-20 17:31     ` Tejun Heo

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=4650CB5E.3010603@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=l.genoni@oltrelinux.com \
    --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 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.