From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Grozdan <neutrino8@gmail.com>
Cc: hancockrwd@gmail.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Fri, 5 Jun 2009 11:42:45 +0100 [thread overview]
Message-ID: <20090605114245.175499e1@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <c5bd819b0906050335i4e813887sc8f4d901da86a1aa@mail.gmail.com>
> 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
next prev parent reply other threads:[~2009-06-05 10:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c5bd819b0906021525l13ee9282j1fb270e141985f66@mail.gmail.com>
2009-06-03 4:05 ` Kernel 2.6.30rc7 limits IDE to UDMA33 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 [this message]
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
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=20090605114245.175499e1@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox