forked from SESA/EBBlib
-
Notifications
You must be signed in to change notification settings - Fork 0
2011 11 30 bringup
Orran Krieger edited this page Dec 1, 2011
·
1 revision
We are doing initial bringup, see picture.
- We use here the words core and EL (Event Location) interchangably.
- When a core starts up, it will exectute the exact same code as every other core, i.e., no assumption of a seperate process for the first and subsequent core.
- The core turns into an EL when the event manager comes up.
- While the LRT code is, obviously, platform specific, we expect to
follow the same model on every platform. This order:
- bring up the pic code, then generate a reset on this core
- carve out memory for this core
- create the translation table on this core
- In the next phase, we initialize all the L0 objects. The order is
the same as the LRT, (figure wrong)
- get Memory Manager up, it will carve rep out of per-core pool, specialized root function for this one object, then we have the ability to dynamcially allocate memory for everyone else
- EBB Mgr
- EventMgr