All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Andreas Mohr <andi@lisas.de>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>
Subject: Re: Kernel 2.6.37 erroneously limiting to UDMA/33
Date: Thu, 06 Jan 2011 10:29:30 -0500	[thread overview]
Message-ID: <4D25DFDA.8010909@earthlink.net> (raw)
In-Reply-To: <20110106103035.GA3484@rhlx01.hs-esslingen.de>

On 01/06/2011 05:30 AM, Andreas Mohr wrote:
> Hi,
>
> Robert Hancock wrote:
>    
>> On 01/05/2011 12:33 PM, Stephen Clark wrote:
>>      
>>> Hello,
>>>
>>> Why is the kernel limiting me to udma/33 when the device says it can do
>>> ata2.01: CFA: TRANSCEND, 20070831, max UDMA/66
>>>
>>> There is no cable the compact flash is a socket on the motherboard!
>>>        
>> The kernel has no way to know that, and presumably the board isn't
>> connecting the signal for IDE pin 34 to ground in order to properly
>> signal that an 80-wire cable (or equivalent) is connected so that speeds
>> over UDMA33 can be used.
>>
>> You should be able to use the libata.force=80c option on the kernel
>> command line to override the cable detection.
>>      
> Further comments for the OP:
>
> If 80c happens to be correct for this machine (since it's soldered
> it's quite obvious) and the machine is quite wide-spread, perhaps one needs
> to add overrides within drivers/ata/pata_via.c/via_cable_detect() functionality,
> analogous to the ata_piix.c/ich_pata_cable_detect() case where it uses
> an entire ich_laptop device list to match against,
> to detect special 80c compatible cases.
>
> But since pata_via.c has the insightful comment
> "Perform cable detection. Actually for the VIA case the BIOS
>   already did this for us."
> it looks like your BIOS might be considered "broken"
> due to not indicating 80c for such a solder job
> -->  BIOS upgrade available?
>
>    
Will check. The machine is an Acrosser AR-M0898B micro box, for use such as
a firewall, vpn appliance, etc.
> And perhaps better avoid mentioning a specific kernel in the subject
> line unless it's a regression (which likely isn't the case here),
> or write it like "..... (on 2.6.XXX)".
>
>    
Good point.

> Andreas Mohr
>
>    


-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)




  reply	other threads:[~2011-01-06 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:33 Kernel 2.6.37 erroneously limiting to UDMA/33 Stephen Clark
2011-01-05 23:50 ` Robert Hancock
2011-01-06 10:30   ` Andreas Mohr
2011-01-06 15:29     ` Stephen Clark [this message]
2011-01-06 15:26   ` Stephen Clark
2011-01-06 18:29   ` Stephen Clark
2011-01-07 20:58     ` Tejun Heo
2011-01-07 12:31   ` Stan Hoeppner
2011-01-06 13:47 ` Alan Cox
2011-01-06 18:20   ` Stephen Clark
2011-01-06 18:22   ` Stephen Clark
  -- strict thread matches above, loose matches on Subject: below --
2011-01-05 20:39 Stephen Clark

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=4D25DFDA.8010909@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=andi@lisas.de \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --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.