capture engine use of workspace_allocate

[Joel Sherrill]

On July 21, 2014 10:44:15 AM CDT, Gedare Bloom <gedare at rtems.org> wrote:
>Either account for it in workspace sizing or use malloc.
>
>On principle, I guess any dynamic allocated memory that isn't mandatory
>to get RTEMS to work should come from malloc.

With one malloc and two workspace allocates, I assumed we should use malloc for all three. 

This is too dynamic for the workspace IMO.


>
>-Gedare
>
>
>On Mon, Jul 21, 2014 at 10:41 AM, Jennifer Averett
><Jennifer.Averett at oarcorp.com> wrote:
>
>The capture engine currently uses a mixture of malloc and 
>
>rtems_workspace_allocate.  We don’t think the workspace
>
>accounts for this, and would like to propose changing it
>
>so that malloc is used for all memory allocation.  Does anyone
>
>see any reason this shouldn’t be done?
>
> 
>
>--jennifer
>
>
>_______________________________________________
>devel mailing list
>devel at rtems.org
>http://lists.rtems.org/mailman/listinfo/devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.