Geode GX1 and IRQ tables

ramesh bios ramesh_bios at
Mon Feb 28 16:39:00 CET 2005

Hi all,

I'd been away for a while. I have picked up another
geode gx1 to play with. Previously I used the
irq_tables from the pcm-5823 and that worked just fine
as far as I could tell. This time around, with this
board I hit trouble. I saw the:

PCI: No IRQ known for interrupt pin A of device

in the log.

And so I ran getpir, replaced the irq_tables.c file,
rebuilt and reflashed. But I still get the same
problem. I tried adding pci=biosirq but the error
still occurs and appears to prevent getting ethernet

Here's what getpir generated from my board. I'm gonna
go try to understand what all of this means. If anyone
has any advice or suggestions on what to do, please do
let me know.



const struct irq_routing_table intel_irq_routing_table
= {
        PIRQ_SIGNATURE,  /* u32 signature */
        PIRQ_VERSION,    /* u16 version   */
        32+16*3,         /* there can be total 3
devices on the bus */
        0x00,            /* Where the interrupt router
lies (bus) */
        (0x12<<3)|0x0,   /* Where the interrupt router
lies (dev) */
        0x1020,          /* IRQs devoted exclusively
to PCI usage */
        0x1078,          /* Vendor */
        0x2,             /* Device */
        0,               /* Crap (miniport) */
        { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, /* u8
rfu[11] */
        0xf6,         /*  u8 checksum , this hase to
set to some value that would give 0 after the sum of
all bytes for this structure (including checksum) */
                /* bus,     dev|fn,   {link, bitmap},
{link, bitmap}, {link, bitmap}, {link, bitmap},  slot,
rfu */
                {0x00,(0x0a<<3)|0x0, {{0x01, 0xdeb8},
{0x02, 0xdeb8}, {0x03, 0xdeb8}, {0x04, 0x0deb8}}, 0x1,
                {0x00,(0x0b<<3)|0x0, {{0x02, 0xdeb8},
{0x03, 0xdeb8}, {0x04, 0xdeb8}, {0x01, 0x0deb8}}, 0x2,
                {0x00,(0x13<<3)|0x0, {{0x01, 0xdeb8},
{0x00, 0xdeb8}, {0x00, 0xdeb8}, {0x00, 0x0deb8}}, 0x0,

Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we.

More information about the coreboot mailing list