PPC403 clock code

[Joel Sherrill]

Nigel Spon wrote:
> I'm going to need to make changes to the PPC403 clock driver code, as
> it assumes that 'ppc405' means PPC405GP, and the PPC405EX has
> different DCRs. The code contains a lot of #ifdefs on (a) the ppc405
> and (b) PPC_HAS_CLASSIC_EXCEPTIONS (ahem). I know RTEMS doesn't
> support 'classic' exceptions any more, so I presume that could come
> out. It looks as though the PPC403 isn't really supported any more
> either, as the helas403 BSP has gone, and the chip isn't sold any more.
>
>   
The hela403 was removed because Thomas didn't have the
resources (or HW debugger) anymore to debug it if it
had been updated to "PIC interrupt model".  

If you can strip the "classic exceptions" and with minor
changes make it work for you that would be better.
> Should I derive a PPC405, new-exceptions-only clock.c and put it in my
> BSP, make minimal modifications to the old code, or follow some other
> course?
>
>   
Ideally targets in RTEMS have a long life.  Many users
come to RTEMS for long life and transitions from old
platforms.  But killing it is an option if it is too much trouble.
> Regards,
>
> ---
> "Its only a model."
>
> Michael Hamel
> ADInstruments Ltd, Dunedin, NZ
>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985