From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932231AbWBFWVB (ORCPT ); Mon, 6 Feb 2006 17:21:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932387AbWBFWVB (ORCPT ); Mon, 6 Feb 2006 17:21:01 -0500 Received: from sccrmhc11.comcast.net ([204.127.200.81]:44712 "EHLO sccrmhc11.comcast.net") by vger.kernel.org with ESMTP id S932231AbWBFWVA (ORCPT ); Mon, 6 Feb 2006 17:21:00 -0500 Message-ID: <43E805D4.5010602@comcast.net> Date: Mon, 06 Feb 2006 21:28:36 -0500 From: Ed Sweetman User-Agent: Debian Thunderbird 1.0.7 (X11/20051019) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alan Cox CC: Harald Dunkel , linux-kernel@vger.kernel.org, "Randy.Dunlap" , akpm@osdl.org Subject: Re: 2.6.16-rc1-mm2 pata driver confusion References: <43E3D103.70505@comcast.net> <43E7A4C0.4020209@t-online.de> <1139255800.10437.51.camel@localhost.localdomain> In-Reply-To: <1139255800.10437.51.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alan Cox wrote: >On Llu, 2006-02-06 at 20:34 +0100, Harald Dunkel wrote: > > >>how it is _supposed_ to work? Is there a conflict between >>ata_piix and piix/mpiix? A short summary could be very helpfull >>to identify problems, and to reduce confusion. >> >> > >MPIIX is totally different PCI identifiers so a different driver. It is >unrelated to any goings on here. > > > Ok, but my nforce board works just fine with pata hdd's but doesn't with atapi devices on the pata bus, which is what his message was in reference to. So forget about piix and such, how are you _supposed_ to get atapi devices seen on the pata drivers (assuming they're functioning at all on the pata drivers) so those that are testing these drivers can make bug reports about them not working, instead of just possibly getting the configuration wrong. No mention of atapi was made in the last patch / status report so i take it You're under the assumption that atapi is _supposed_ to be working in pata (at least the drives should be initialized and brought up). So if any info is needed, just mention what it is... the drivers have been rock solid so far for my sata and pata hdds. I'd like to continue testing with the atapi drive detected because I can't have both ide and pata drivers loaded at the same time, and switching between the two changes device names around.