New Work Area Initialization API

[Gedare Bloom]

I skimmed the patch series and saw no obvious issues.

Overall, I like the change. It unifies more of the bsp startup code,
and if it later permits the use of malloc sooner then it may help with
generalizing the bsp_early_malloc in sparc.

I saw one BSP that uses the new feature. Is there any documentation of
how to use the feature, or maybe just a pointer to that BSP for the
interested BSP-developer?

-Gedare

On Mon, Oct 15, 2012 at 9:04 AM, Sebastian Huber
<sebastian.huber at embedded-brains.de> wrote:
> The work areas (RTEMS work space and C program heap) will be initialized now in
> a separate step and are no longer part of rtems_initialize_data_structures().
> Initialization is performed with tables of Heap_Area entries.  This allows
> usage of scattered memory areas present on various small scale
> micro-controllers.
>
> The sbrk() support API changes also.  The bsp_sbrk_init() must now deal with a
> minimum size for the first memory chunk to take the configured work space size
> into account.
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel