From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Helgaas Subject: Re: CSB5 IDE does not fully support native mode?? Date: Thu, 26 May 2005 10:55:38 -0600 Message-ID: <200505261055.38137.bjorn.helgaas@hp.com> References: <200505242026.DJT32107@ms3.netsolmail.com> <1117117463.5743.149.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from atlrel9.hp.com ([156.153.255.214]:10145 "EHLO atlrel9.hp.com") by vger.kernel.org with ESMTP id S261604AbVEZQzu (ORCPT ); Thu, 26 May 2005 12:55:50 -0400 In-Reply-To: <1117117463.5743.149.camel@localhost.localdomain> Content-Disposition: inline Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Alan Cox Cc: evt@texelsoft.com, Linux Kernel Mailing List , linux-ide@vger.kernel.org On Thursday 26 May 2005 8:24 am, Alan Cox wrote: > In order to keep the legacy world from falling to bits IDE and VGA have > some ugly hacks in the PCI spec. > > In legacy mode an IDE device appears at the "old" standard IDE addresses > and uses an external IRQ pin wired to the ISA IRQ lines (14 or 15). In > native mode it behaves like a PCI device, honouring the PCI bars and > using the PCI INT lines. This has been niggling in my mind for a while -- in legacy mode, the device should use IRQ 14/15. But I think we still call pci_enable_device(), which sets up IRQ routing according to the usual PCI rules. Should we be using pci_enable_device() at all in legacy mode?