> No. Could we please integrate this not with ACPI, but with the much more
> limited "arch/i386/kernel/acpitable.c", which does NOT imply full ACPI,
> only scanning the tables for information in static format (like the irq
> routing stuff).
Unfortunately, the PCI interrupt routing stuff in ACPI is not in a static
table, but needs the full-blown AML interpreter. Bad, but we can't do
anything about it.
> That we can/will/should always enable, and we should NOT EVER encourage
> this kind of "per-BIOS" crud. That just becomes a total horror to maintain
> in the long run.
There's one thing which may be worth doing, I think someone else did
suggest this before: Allow for overriding BIOS tables with user provided
correct ones. In this case, Jes could add an entry for the PCMCIA bridge
to the $PIR table and tell the kernel to use this instead of the buggy
BIOS' one.
The question is how to do this cleanly. Of course, it's easy enough to
invent some way to use a corrected table which is linked into vmlinux at
compile time. However, that means that the user has to recompile his
kernel to add the table, which is not an easy option for everyone.
It would be nicer to dynamically add the table, e.g. have the bootloader
load it, kind of like the initrd, but that seems not possible without a
lot of effort. (Or is the initrd protocol flexible enough to allow for
this?)
--Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/