From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756461AbZEZOkJ (ORCPT ); Tue, 26 May 2009 10:40:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755400AbZEZOkB (ORCPT ); Tue, 26 May 2009 10:40:01 -0400 Received: from [222.92.8.141] ([222.92.8.141]:34859 "EHLO lemote.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753736AbZEZOkA (ORCPT ); Tue, 26 May 2009 10:40:00 -0400 Subject: Re: [loongson-PATCH-v1 24/27] fixup for FUJITSU disk From: yanh Reply-To: yanh@lemote.com To: Alan Cox Cc: "Martin K. Petersen" , Sergei Shtylyov , Bartlomiej Zolnierkiewicz , =?gb2312?Q?=BA=FA=BA=E9=B1=F8?= , wuzhangjin@gmail.com, linux-mips@linux-mips.org, Ralf Baechle , IDE/ATA development list , Linux Kernel , linux-scsi , Philippe Vachon , Zhang Le , Zhang Fuxin , Arnaud Patard , loongson-dev@googlegroups.com, gnewsense-dev@nongnu.org, Nicholas Mc Guire , Liu Junliang , Erwan Lerale In-Reply-To: <20090526085605.014d0087@lxorguk.ukuu.org.uk> References: <1243230339.9819.18.camel@localhost.localdomain> <4A1A4A54.6090401@lemote.com> <200905251656.25357.bzolnier@gmail.com> <4A1AEBF7.7040402@ru.mvista.com> <1243300890.9819.40.camel@localhost.localdomain> <20090526085605.014d0087@lxorguk.ukuu.org.uk> Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 May 2009 22:39:32 +0800 Message-Id: <1243348772.9819.77.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1 (2.24.1-2.fc10) Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2009-05-26二的 08:56 +0100,Alan Cox写道: > > > In any case I have yet to see a CS5536 system whose BIOS sets the cable > > > detection bit. If that's the problem I guess we could add a quirk flag > > > to override the (lack of) BIOS setting. > > > > > This may be the cause that udma5 cannot be set. > > > If the system doesn't have working BIOS cable detect as per the > documentation for the chip then just return the "unknown" cable type and > libata will do device side cable detect. After force cable type as 80 wire, udma5 can be set OK now. after some raw test, the legacy and native driver have no obvious difference in performance. Remain issue: this native driver still have suspend/resume issue. > > Alan