Re: eCos port to Freescale MAC7100

[Andrew Lunn <andrew at lunn dot ch>]

> >We will first need a copyright assignment. Please could you take a
> >look at http://ecos.sourceware.org/assign.html. 
> >  
> OK. We'll do it. Please send me the document/template/instructions.

See the URL i said above!

> I tried to follow instructions and fashion in which eCos ports are made 
> so I guess it shall not be hard for you to track it.

O.K. Thart is good.

> Also I have some questions regarding organization of some packages. 
> Namely most of MAC7100 peripherals are (or will be) also implemented on 
> other Freescale chips, but with different architecture: PowerPC (MPC5500 
> family), ColdFire, so it would be useful to enable sharing of driver 
> sources. Therefore I created ...devs/serial/freescale/esci directory 
> rather than .../mac7100/.... I plan to do so for watchdog too.

This is fine. You might also want to take a look at 

http://ecos.sourceware.org/ml/ecos-patches/2005-11/msg00016.html

It is still on my TODO list to get this intergrated into anoncvs. Can
any code be shared with this?

> The 
> question is what to do with interrupt controller (INTC). As far as i 
> have seen in eCos repository interrupt controller software is bonded 
> with respective variant (or platform). The rationale is that interrupt 
> controllers are more closely bonded to processors than other 
> peripherals. I have followed this approach but might try to place INTC 
> sources elsewhere, thus make it sharable with other architectures.

This is not normal. But that should not stop you from doing it. I
guess you will want to keep hal_platform_ints.h in the HAL, but move
the hal_interrupt_* from the <HAL>_misc.c file into your INTC package.

There is also the question of where to put the new package in the eCos
tree. eg packages/dev/interrupt/freescale, or
packages/hal/shared/freescale etc.

     Andrew