[CFT] CONFIG_ALL_PPC and post-PReP (MVME2600, etc) systems

Hey all.  I've just commited code to the linuxppc-2.5, linuxppc_2_4 and
linuxppc_2_4_devel trees which should fix the problem seen when a
CONFIG_ALL_PPC kernel is booted on a machine which is identified as
'prep' but lacks an MPC10x.  I've tested my PowerStack, and it still
works, but I'm unsure as to:
a) Does this fix the problem seen on MVME2600?  I would assume so.
b) The broken HW which caused us to go from polling to int-ack, what
host bridge was this exactly?  We currently use the MPC10x-specific
address on MPC105/MPC106/MPC107 (completeness), and based on the
original comment I assume that it was MPC10x HW.  Can someone confirm?
Thanks.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

On Thu, 2002-11-07 at 13:14, Tom Rini wrote:

Hey all.  I've just commited code to the linuxppc-2.5, linuxppc_2_4 and
linuxppc_2_4_devel trees which should fix the problem seen when a
CONFIG_ALL_PPC kernel is booted on a machine which is identified as
'prep' but lacks an MPC10x.  I've tested my PowerStack, and it still
works, but I'm unsure as to:
a) Does this fix the problem seen on MVME2600?  I would assume so.
b) The broken HW which caused us to go from polling to int-ack, what
host bridge was this exactly?  We currently use the MPC10x-specific
address on MPC105/MPC106/MPC107 (completeness), and based on the
original comment I assume that it was MPC10x HW.  Can someone confirm?

Sure, it was MPC105.

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/