[RTEMS Project] #3838: Rework work area initialization

[RTEMS trac]

#3838: Rework work area initialization
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  enhancement      |      Status:  assigned
 Priority:  normal           |   Milestone:  5.1
Component:  bsps             |     Version:  5
 Severity:  normal           |  Resolution:
 Keywords:                   |  Blocked By:
 Blocking:  3835             |
-----------------------------+------------------------------

Comment (by Sebastian Huber):

 Replying to [comment:3 Chris Johns]:
 > Replying to [comment:2 Sebastian Huber]:
 > > I am not sure what needs to be explained in more detail. This is
 mostly a mechanical change which just rearranges existing things a bit
 differently.
 >
 > I think there are somethings, for example take "components are
 initialized on demand", what is a "component" and what does "initialized
 on demand" mean?

 The two components are the workspace and the C program heap. On demand
 means that they are only initialized if functions of these components are
 used by the application.

 >
 > I am OK with working through the detail but this will have to wait until
 I find the time. If you do not mind waiting let me know.
 >
 > > As usual, maintainers of BSPs which are not in the mainline RTEMS
 source have to pay a price and have to update their BSPs by themself. With
 an updated documentation, this shouldn't be an issue.
 >
 > A number of users cannot submit their BSPs and we have attempted to
 maintain a BSP API. Maybe we should define a formal BSP interface that
 cannot be touched without careful consideration?

 I do this with careful consideration. This change request is the result of
 a multi year work consisting of lots of small steps to make it possible to
 fully statically initialize RTEMS. Yes, it breaks the API, but adopting an
 existing BSP can be done easily in less than one hour. Also if you use a
 standard linker command file, then you can use the default implementation
 in your external BSP.

--
Ticket URL: <http://devel.rtems.org/ticket/3838#comment:4>
RTEMS Project <http://www.rtems.org/>
RTEMS Project