Hello Maciej,
17.08.2021 1:30, Maciej W. Rozycki:
[...]
If you have a look through /dev/mem and see if there's a "$PIR" signature
somewhere (though not a Linux kernel area of course), then we may know for
sure.
There is no "$PIR" signature anywhere, including all uncompressed
internal ROM modules. Instead though, there is an "$IRT" signature and a
table following it:
F9A90: 24 49 52 54 04 04 00 00 00 18 10 F8 DE 28 F8 DE │ $IRT
F9AA0: 41 F8 DE 89 F8 DE 01 00 00 20 28 F8 DE 41 F8 DE │
F9AB0: 89 F8 DE 10 F8 DE 02 00 00 28 41 F8 DE 89 F8 DE │
F9AC0: 10 F8 DE 28 F8 DE 03 00 00 08 89 F8 DE 10 F8 DE │
F9AD0: 28 F8 DE 41 F8 DE 04 00 00 09 03 0A 04 05 07 06 │
F9AE0: 00 0B 00 0C 00 0E 00 0F 60 1E 0E 1F E8 98 00 8B │
F9AF0: FA 1F 72 6B 0A C0 74 67 3C F0 73 45 8A C8 24 01 │
By stepping through some BIOS initialization code in bochs, I've
determined that this table is being consulted just before modifying
chipset registers 44 and 42/43, so no doubt it is related to IRQs. From
the same BIOS code it is clear that every entry is 16 bytes long (just
like in pci_x86.h), the very first entry starts at offset 8 (counting
from the start of the above fragment), and total number of entries is
stored at offset 5 in a 16-bit word. My guess is 0-value byte at offset
7 might be padding, and 4 at offset 4 looks like header size, because
there is just nothing else in the header.
The entries look similar to irq_info defined in pci_x86.h, so I decided
to give it a try. For a test, I've modified the struct irq_routing_table
defined in pci_x86.h and irq.c to match this $IRT structure. Now I get this:
[ 0.312000] PCI: IRQ init
[ 0.316000] PCI: Interrupt Routing Table found at 0xc00f9a90
[ 0.316000] 00:03 slot=01
[ 0.316000] 0:10/def8
[ 0.316000] 1:28/def8
[ 0.316000] 2:41/def8
[ 0.316000] 3:89/def8
[ 0.316000] 00:04 slot=02
[ 0.316000] 0:28/def8
[ 0.316000] 1:41/def8
[ 0.316000] 2:89/def8
[ 0.316000] 3:10/def8
[ 0.316000] 00:05 slot=03
[ 0.316000] 0:41/def8
[ 0.316000] 1:89/def8
[ 0.316000] 2:10/def8
[ 0.320000] 3:28/def8
[ 0.320000] 00:01 slot=04
[ 0.320000] 0:89/def8
[ 0.320000] 1:10/def8
[ 0.320000] 2:28/def8
[ 0.320000] 3:41/def8
[ 0.320000] PCI: Attempting to find IRQ router for [0000:0000]
[ 0.320000] PCI: Trying IRQ router for [10b9:1489]
[ 0.320000] pci 0000:00:00.0: FinALi IRQ router [10b9:1489]
Not sure if the table was parsed correcly, but the following messages
later obviously show some problem:
[ 0.625911] 8139too 0000:00:03.0: runtime IRQ mapping not provided by
arch
[ 0.625911] 8139too: 8139too Fast Ethernet driver 0.9.28
[ 0.625911] 8139too 0000:00:03.0: PCI INT A -> PIRQ 10, mask def8,
excl 0000
[ 0.625911] 8139too 0000:00:03.0: PCI INT A -> newirq 11
[ 0.630068] PCI: setting IRQ 15 as level-triggered
[ 0.630068] -> edge
[ 0.630068] 8139too 0000:00:03.0: found PCI INT A -> IRQ 15
[ 0.630068] 8139too 0000:00:03.0: IRQ routing conflict: have IRQ 11,
want IRQ 15
[ 0.641901] 8139too 0000:00:03.0 eth0: RealTek RTL8139 at 0xc2582f00,
00:11:6b:32:85:74, IRQ 11
First, INTA is apparently routed to IRQ11 (and the network card works
just fine with that), whereas pci code wants IRQ15 for some reason.
Second, dumping chipset reg 44 shows that INTA is still set to EDGE mode
anyway, although dumping port 4D1 now shows IRQ15 was changed to LEVEL
mode, exactly as indicated in the above output. I'm not sure, but the
datasheet (page 77) seems to indicate that INTx mode set in reg 44
should match the respective IRQx mode in port 4Dx (Although the ROM BIOS
seems to only have code to change triggering mode in the 44 register and
does not care about port 4Dx whatsoever, which kinda contradicts the
datasheet)
I'll do some more digging later, but any hints are appreciated anyway.
Thank you,
Regards,
Nikolai
I'm a little busy at the moment with other stuff and may not be able to
look into it properly right now. There may be no solution, not at least
an easy one. A DMI quirk is not possible, because:
DMI not present or invalid.
There is a PCI BIOS:
PCI: PCI BIOS revision 2.10 entry at 0xf6f41, last bus=0
however, so CONFIG_PCI_BIOS just might work. Please try that too, by
choosing CONFIG_PCI_GOANY or CONFIG_PCI_GOBIOS (it may break things
horribly though I imagine).
Maciej
