Can someone explain what the issue is and what I might need to
do to use csb5 ide in native mode? thanks.
- Eric van Tassell
On Maw, 2005-05-24 at 21:26, [email protected] wrote:
> Can someone explain what the issue is and what I might need to
> do to use csb5 ide in native mode? thanks.
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.
>From a performance perspective the difference is essentially irrelevant
and from a wiring perspective its often decided irrevocably by the board
maker.
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?
On Iau, 2005-05-26 at 17:55, Bjorn Helgaas wrote:
> 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?
For all the other enables yes. The IRQ is an interesting case and I'd
have to look into the newer code to even guess - Bartlomiej has probably
has a much better idea as maintainer.