Luoqi Chen 4522ac77de SATA device on some nForce based boards could get confused if MSI is not ... used but MSI to HyperTransport IRQ mapping is enabled, and would act as if MSI is turned on, resulting in interrupt loss. This commit will, 1. enable MSI mapping on a device only when MSI is enabled for that device and the MSI address matches the HT mapping window. 2. enable MSI mapping on a bridge only when a downstream device is allocated an MSI address in the mapping window PR: kern/118842 Reviewed by: jhb MFC after: 1 week		2008-07-23 09:44:36 +00:00
..
eisa_pci.c
fixup_pci.c
hostb_pci.c
ignore_pci.c
isa_pci.c
pci_if.m
pci_pci.c	SATA device on some nForce based boards could get confused if MSI is not	2008-07-23 09:44:36 +00:00
pci_private.h	Make the PCI code aware of PCI domains (aka PCI segments) so we can	2007-09-30 11:05:18 +00:00
pci_user.c	Don't cache the new-bus name of a PCI device in the PCI conf structure,	2008-01-15 21:40:46 +00:00
pci.c	SATA device on some nForce based boards could get confused if MSI is not	2008-07-23 09:44:36 +00:00
pcib_if.m
pcib_private.h	Make the PCI code aware of PCI domains (aka PCI segments) so we can	2007-09-30 11:05:18 +00:00
pcireg.h
pcivar.h	SATA device on some nForce based boards could get confused if MSI is not	2008-07-23 09:44:36 +00:00
vga_pci.c