From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932198AbWGGROa (ORCPT ); Fri, 7 Jul 2006 13:14:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932193AbWGGROa (ORCPT ); Fri, 7 Jul 2006 13:14:30 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:61161 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S932198AbWGGROa (ORCPT ); Fri, 7 Jul 2006 13:14:30 -0400 Message-ID: <44AE966F.8090506@garzik.org> Date: Fri, 07 Jul 2006 13:14:23 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.4 (X11/20060614) MIME-Version: 1.0 To: Alan Cox CC: "Randy.Dunlap" , jamagallon@ono.com, akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: 2.6.17-mm6 References: <20060703030355.420c7155.akpm@osdl.org> <20060705234347.47ef2600@werewolf.auna.net> <20060705155602.6e0b4dce.akpm@osdl.org> <20060706015706.37acb9af@werewolf.auna.net> <20060705170228.9e595851.akpm@osdl.org> <20060706163646.735f419f@werewolf.auna.net> <20060706164802.6085d203@werewolf.auna.net> <20060706234425.678cbc2f@werewolf.auna.net> <20060706145752.64ceddd0.akpm@osdl.org> <1152288168.20883.8.camel@localhost.localdomain> <20060707175509.14ea9187@werewolf.auna.net> <1152290643.20883.25.camel@localhost.localdomain> <20060707093432.571af16e.rdunlap@xenotime.net> <1152292196.20883.48.camel@localhost.localdomain> In-Reply-To: <1152292196.20883.48.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.3 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alan Cox wrote: > Also its dangerous to assume "pata_*" is a PATA driver, it may be SATA > with a bridge chip, and in some cases like the ATI this is quite common. Incorrect; what you describe is the core assumption underlying the "ata_", "pata_", and "sata_" prefixes. If the user can attached PATA and SATA devices to a controller, its prefix is ata_ If the user can only attach PATA devices, its prefix is pata_ If the user can only attach SATA devices, its prefix is sata_ For the purposes of this convention, user-attached bridges such as PATA<->SATA bridges, are ignored. Most older controllers always fall into pata_, most newer into sata_, and an odd few ata_ Its a bug if you don't help maintain these assumptions :) Jeff