Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965006AbWIENaz (ORCPT ); Tue, 5 Sep 2006 09:30:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965013AbWIENay (ORCPT ); Tue, 5 Sep 2006 09:30:54 -0400 Received: from mxsf11.cluster1.charter.net ([209.225.28.211]:47243 "EHLO mxsf11.cluster1.charter.net") by vger.kernel.org with ESMTP id S965006AbWIENax (ORCPT ); Tue, 5 Sep 2006 09:30:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17661.31750.457301.687508@smtp.charter.net> Date: Tue, 5 Sep 2006 09:30:46 -0400 From: "John Stoffel" To: Alan Cox Cc: Jeff Garzik , "linux-ide@vger.kernel.org" , Linux Kernel , Andrew Morton , Linus Torvalds Subject: Re: PATA drivers queued for 2.6.19 In-Reply-To: <1157371363.30801.31.camel@localhost.localdomain> References: <44FC0779.9030405@garzik.org> <1157371363.30801.31.camel@localhost.localdomain> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1023 Lines: 26 >>>>> "Alan" == Alan Cox writes: Alan> Ar Llu, 2006-09-04 am 07:01 -0400, ysgrifennodd Jeff Garzik: >> The following must be in all caps, though: >> >> drivers/ide IS STILL THE PATA DRIVER SET THAT USERS AND DISTROS SHOULD >> CHOOSE. Alan> Except optionally for the following for chips not handled by or broken Alan> totally in drivers/ide: Alan> pata_mpiix - some early pentium era laptops Alan> pata_oldpiix - original "PIIX" chipset Alan> pata_radisys - embedded chipset What about pata_hpt37x and it's failure to work with my HPT302 Rev one controller? I admit it could be just an IRQ problem, but since 2.6.18-rc5-mm1 works with the old ide/pci/hpt366.c, but not with the new version? It's using the same interrupt each time too. John - 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/