cvs commit: src/sys/dev/acpica acpi_pci_link.c acpi_pcib.c
acpi_pcib_acpi.c acpi_pcib_pci.c acpi_pcibvar.h
nate at root.org
Wed Aug 11 12:54:00 PDT 2004
John Baldwin wrote:
> On Wednesday 11 August 2004 01:40 pm, Nate Lawson wrote:
>>Daniel Eriksson wrote:
>>>atapci0: <HighPoint HPT374 (channel 0+1) UDMA133 controller> port
>>>11 atapci1: <HighPoint HPT374 (channel 2+3) UDMA133 controller> port
>>>11 ahc0: <Adaptec 29160 Ultra160 SCSI adapter> port 0x9400-0x94ff mem
>>>0xed800000-0xed800fff irq 3 at device 12.0 on pci0
>>>atapci2: <HighPoint HPT374 (channel 0+1) UDMA133 controller> port
>>>10 atapci3: <HighPoint HPT374 (channel 2+3) UDMA133 controller> port
>>>10 at device 14.1 on pci0
>>>atapci4: <VIA 6420 SATA150 controller> port
>>>800 -0x5807 irq 5 at device 15.0 on pci0
>>>atapci5: <VIA 8237 UDMA133 controller> port
>>>0x3800-0x380f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 14 at device 15.1
>>>ata0: at 0x1f0 irq 14 on atapci5
>>>ata1: at 0x170 irq 15 on atapci5
>>I need the dmesg output from boot -v to see the link priority settings.
> He's using an I/O APIC. These are probably all entries that don't have a link
> device but just a hardwired global interrupt number. Did you test that case?
I don't have an APIC but acpi_pcib_route_interrupt() still checks Source
== NULL and *Source == '\0' and if so, treats SourceIndex as hardwired.
Also, acpi_pci_link_config() doesn't add entries to its PRT list if
the irq is hardwired. This logic didn't change in the commit.
More information about the freebsd-current