Re: xl device doesn't work with ACPI enabled under -current and -stable

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:PCIB_ROUTE_INTERRUPT calls the way up to pci_cfgintr.
:pci_cfgintr first checks via pci_cfgintr_valid if a valid interrupt
:already exists, which doesn't happen here.
:It checks pci_cfgintr_linked next, which whould find the mapping for xl0
:and stop using that link. This doesn't somehow happen.
:
:The strange part and the reason why I suspect the ACPI tables [which
:I still haven't looked into] is the different configuration of the
:secondary PCI bus at the time of cbb probe. Another strange part is
:the different subordinatebus / secondarybus field. I have to start
:reading the PCI specs now.
:
:Joerg

    Hmm.  It's having to use the $PIR table, right?

    The $PIR table for the secondary bus does not look correct.  Since
    routing CBB0's IRQ seems to blow up XL0's IRQ, I would expect the Link
    field for CBB0 and XL0 to be the same.  But it isn't:

    Location  Bus Device Pin  Link  IRQs
    embedded    2    0    A   0x62  3 4 5 6 7 9 10 11 12 14 15  (XL0)
    embedded    2    1    A   0x63  3 4 5 6 7 9 10 11 12 14 15  (CBB0)

    Is it possible for the same intX line for two PCI devices on the same bus 
    to be routed to different pins ?  I guess it must be.

    So, in anycase, if my interpretation of the $PIR table is correct, then
    the $PIR table on that machine is plain wrong.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>