Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762805AbYHDV1o (ORCPT ); Mon, 4 Aug 2008 17:27:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758870AbYHDV0L (ORCPT ); Mon, 4 Aug 2008 17:26:11 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:37513 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753273AbYHDV0K (ORCPT ); Mon, 4 Aug 2008 17:26:10 -0400 Date: Mon, 4 Aug 2008 22:06:19 +0100 From: Alan Cox To: Robert Hancock Cc: Bartlomiej Zolnierkiewicz , James Bottomley , ksummit-2008-discuss@lists.linux-foundation.org, linux-kernel , linux-ide , Jeff Garzik Subject: Re: Kernel Summit request for Discussion of future of ATA (libata) and IDE Message-ID: <20080804220619.76b94ceb@lxorguk.ukuu.org.uk> In-Reply-To: <48977200.3050307@shaw.ca> References: <48976168.3020804@shaw.ca> <20080804205508.20a3f917@lxorguk.ukuu.org.uk> <48977200.3050307@shaw.ca> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; x86_64-redhat-linux-gnu) Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 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: 1409 Lines: 32 > I guess that bit doesn't really make any difference with remotely modern > drives, then.. Could we make that ata_id_has_dword_io check always > return true if ata_id_is_ata returns true and only check word 48 if not? I suspect (but need to dig further) that ata_id_has_dword_io should only be called by pata_legacy. > I saw Willy Tarreau's patch from February for this, I agree that we > should likely use a separate data_xfer method for 32-bit transfer (or if > enough controllers should support 32-bit, then just make it be the > default and make a separate 16-bit only function for those that don't), > rather than punting the decision to the user with hdparm. Definitely. > You mentioned in the thread for Willy's patch that "some > controllers have quirky rules for 32bit xfers" - any details anywhere? There are two main ones - Some controllers only support 32bit I/O for a multiple of 32bit values [sometimes 'unless the fifo is disabled']. I'd have to go back over the docs but I think the AMD may be one of those - Some controllers (VLB generally) require a magic sequence before the transfer. You'll see that in the pata_legacy bits. Alan -- 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/