Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753456AbZFEKlz (ORCPT ); Fri, 5 Jun 2009 06:41:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751636AbZFEKlr (ORCPT ); Fri, 5 Jun 2009 06:41:47 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:55603 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750999AbZFEKlq (ORCPT ); Fri, 5 Jun 2009 06:41:46 -0400 Date: Fri, 5 Jun 2009 11:42:45 +0100 From: Alan Cox To: Grozdan Cc: hancockrwd@gmail.com, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33 Message-ID: <20090605114245.175499e1@lxorguk.ukuu.org.uk> In-Reply-To: References: <4A25F688.9000407@gmail.com> <20090603131407.57c490ed@lxorguk.ukuu.org.uk> <20090603140140.491a8ea8@lxorguk.ukuu.org.uk> <20090605100505.41b3b818@lxorguk.ukuu.org.uk> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 906 Lines: 22 > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/