In article <43FE0B99.2000708@tadpole.com>
garrett_damore@tadpole.com wrote:

> We have a sanity check already -- the link will fail due to multiple
> symbol definitions. :-)

Well, that doesn't indicate what is wrong exactly.

> I am generally *not* fond of #ifdef jungles, and your proposal creates
> two of them.
> 
> The other problem with this is that I can imagine having a board
> defintion that actually supports a board *family* (where the type of
> board is run-time detectable via a register), and then what do you do? 

Maybe MI board_info() can call board specific xxx_board_info()
funtcions? Some of examples are ofppc/ofppc/platform.c and
pmax/pmax/sysconf.c etc.
---
Izumi Tsutsui