Interrupt routing in prep_pci.c

Cort Dougan cort at
Tue Feb 23 05:25:04 EST 1999

Before you get too grumpy please realize I don't have any of the newer
boards.  I only have the "old interrupt" routing scheme boards to work
with first hand.  If someone wants to get to me 1) the newer boards or 2)
some code that handles both well I'd be more than happy to redo the
routing.  prep_pci.c has been a nasty piece of code for some time.

}OK but with the current code :
}   1) you scew up the value that may have been correctly set for PCI devices,
}   2) You force epople to write a config for each board,
}   3) you assume old 105, 106 PCI interrupt routing scheme that makes nothing
}   on newer chips like raven,

That's right, we should keep the setup if it's correct.  Find me a better
scheme for identifying the board, then.

}	1) we should know wether the board firmware correctly
}	set up the PCI devices. If this is the case, the old
}	interrupt scheme must be removed. Note that this
}	implies to have a better scheme for identifying board than the
}	inb (0x800) currently used.

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request at ]]

More information about the Linuxppc-dev mailing list