From: Robert Hancock <hancockr@shaw.ca>
To: l.genoni@oltrelinux.com, linux-kernel <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, htejun@gmail.com
Subject: Re: something strange in libata-core.c for kernel 2.6.22-rc3
Date: Sun, 20 May 2007 11:18:34 -0600 [thread overview]
Message-ID: <465082EA.1040603@shaw.ca> (raw)
In-Reply-To: <fa.LXy58QwLlPXDhsfVUU9kEfA3QbI@ifi.uio.no>
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?
>
> --- libata-core.c.orig 2007-05-20 14:31:25.000000000 +0200
> +++ libata-core.c 2007-05-20 14:34:01.000000000 +0200
> @@ -3901,8 +3901,7 @@
> /* UDMA/44 or higher would be available */
> if((ap->cbl == ATA_CBL_PATA40) ||
> (ata_drive_40wire(dev->id) &&
> - (ap->cbl == ATA_CBL_PATA_UNK ||
> - ap->cbl == ATA_CBL_PATA80))) {
> + (ap->cbl == ATA_CBL_PATA_UNK))) {
> ata_dev_printk(dev, KERN_WARNING,
> "limited to UDMA/33 due to 40-wire
> cable\n");
> xfer_mask &= ~(0xF8 << ATA_SHIFT_UDMA);
It only does that for ATA_CBL_PATA80 if ata_drive_40wire returns true,
which means that the drive is detecting a 40-wire cable on its side.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-05-20 17:18 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 ` Robert Hancock [this message]
[not found] ` <fa.Ldjy2OubeKomZD0OV2gRm/wpUFo@ifi.uio.no>
2007-05-20 22:27 ` something strange in libata-core.c for kernel 2.6.22-rc3 Robert Hancock
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=465082EA.1040603@shaw.ca \
--to=hancockr@shaw.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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).