"Eric W. Biederman" wrote:
>
>
> In my limited experience having a non functioning interrupt is caused
> by having a bad or missing pirq routing table. If there is
> useful information that lscpi can grab I haven't seen it.
>
> Last time I looked in linuxBIOS we don't setup any irqs,
> so the kernel must do everything.
>
> A pci card has no choice as to which irq it sends.
>
> Usually there is an irq router that takes interrupt lines from
> the various slots and maps them to irqs.
>
> Eric
2.4.x kernel is smart enough to scan and parse the PIRQ table reside in 0xf0000.
In LinuxBIOS we just copy the PIRQ table from DoC to F segment and let the kernel
do the rest things. I really have no idea how to do this in 2.2.x kernel.
P.S. Actually I don't understand the PIRQ very well niether. I just dump it from
normal AWARD bios and "manually" translate it to C. I am working on a utility
which can scan your F segment and generate the PIRQ table.
Ollie
