Date: Fri, 6 Sep 2002 10:08:08 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/i386/include pci_cfgreg.h src/sys/i386/pci pci_bus.c pci_cfgreg.c Message-ID: <200209061708.g86H88as092198@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
jhb 2002/09/06 10:08:08 PDT
Modified files:
sys/i386/include pci_cfgreg.h
sys/i386/pci pci_bus.c pci_cfgreg.c
Log:
- Add a pci_cfgintr_valid() function to see if a given IRQ is a valid
IRQ for an entry in a PCIBIOS interrupt routing ($PIR) table.
- Change pci_cfgintr() to except the current IRQ of a device as a fourth
argument and to use that IRQ for the device if it is valid.
- If an intpin entry in a $PIR entry has a link of 0, it means that that
intpin isn't connected to anything that can trigger an interrupt. Thus,
test the link against 0 to find invalid entries in the table instead of
implicitly relying on the irqs field to be zero. In the machines I have
looked at, intpin entries with a link of 0 often have the bits for all
possible interrupts for PCI devices set.
Revision Changes Path
1.7 +1 -1 src/sys/i386/include/pci_cfgreg.h
1.86 +2 -1 src/sys/i386/pci/pci_bus.c
1.90 +33 -1 src/sys/i386/pci/pci_cfgreg.c
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209061708.g86H88as092198>
