From: Robert Hancock <hancockrwd@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Grozdan <neutrino8@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Fri, 05 Jun 2009 19:07:47 -0600 [thread overview]
Message-ID: <4A29C163.3080706@gmail.com> (raw)
In-Reply-To: <20090605114245.175499e1@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> I've relayed your reply to the pata_amd user on the forum. As for my
>> case with pata_via, until this is fixed, is there any way to force it
>> to use a higher UDMA? Is there a flag that can be passed in, for
>
> In your case given the BIOS appears to be informing us you have a 40wire
> cable there isn't much that can be fixed
>
>> example, in /sys somewhere? hdparm fails to set a higher UDMA and I
>> looked at sdparm but don't see anything in it to increase UDMA...
>
> Tejun some time ago added stuff to override all of these things:
>
> See Documentation/kernel-parameters.txt
>
> libata.force=
>
> which will let you override all sorts of autodetection for quirky boards
I wouldn't rule out the possibility of a bug. The code in pata_via looks
a bit fishy, it reports a 40-wire cable if either the GTM data wasn't
present or valid, or if it reports a mode of UDMA2 or less. In the
former case it seems like ATA_CABLE_PATA_UNK would be the safer choice
since we really don't know, and we should then use drive-side detection,
rather than assuming a 40-wire cable by default..
next prev parent reply other threads:[~2009-06-06 1:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 22:25 Kernel 2.6.30rc7 limits IDE to UDMA33 Grozdan
2009-06-03 4:05 ` Robert Hancock
2009-06-03 11:35 ` Grozdan
2009-06-03 12:14 ` Alan Cox
2009-06-03 12:52 ` Grozdan
2009-06-03 13:01 ` Alan Cox
2009-06-03 13:15 ` Grozdan
2009-06-03 13:39 ` Grozdan
2009-06-04 14:50 ` Grozdan
2009-06-05 9:05 ` Alan Cox
2009-06-05 10:35 ` Grozdan
2009-06-05 10:42 ` Alan Cox
2009-06-05 12:43 ` Grozdan
2009-06-05 13:21 ` Alan Cox
2009-06-05 14:02 ` Grozdan
2009-06-06 1:07 ` Robert Hancock [this message]
2009-06-06 14:56 ` Alan Cox
2009-06-06 18:16 ` Robert Hancock
2009-06-06 22:08 ` Alan Cox
2009-06-07 4:39 ` Grozdan
[not found] ` <4A2BF785.3020402@gmail.com>
2009-06-07 18:24 ` Grozdan
2009-06-07 18:46 ` Michael S. Zick
2009-06-07 19:54 ` Alan Cox
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=4A29C163.3080706@gmail.com \
--to=hancockrwd@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neutrino8@gmail.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.