Re: Porting eCos to PPC 405cr board

[Gary Thomas <gary at mlbassoc dot com>]

On Mon, 2003-11-03 at 04:39, Tue Brems Olesen wrote:
> Hello,
> 
> I am in the process of porting eCos to a board with a PowerPC 405cr
> processor.
> 
> Currently, eCos supports the PPC 405GP processor, which has built-in PCI
> bus and ethernet controller. The PCI subsystem is initialized in the
> ppc40x variant code (packages/hal/powerpc/ppc40x/current/include/var_io.h).
> 
> However, the PPC 405CR processor has neither PCI bus or ethernet
> controller. Hence, the HAL code should not try to initialize them.
> 

and it won't if you don't include those packages!

> My question is: Which method is best for solving the problem: 
> 
> 1) Wrap the 405GP / 405CR specific code in #define's, keeping all
>    code for the different PPC 405 chips in one common file,
> 
> or:
> 
> 2) Create a 405CR-specific variant of the eCos HAL, in a separate
>    directory tree in the packages/hal/powerpc structure.
> 
> 
> (any better suggestions are, of course, very much appreciated)

Choice (1) is correct.  Note: eCos does run on other 405 processors,
the code just is not public (BTW, this is common for a lot of eCos)

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates