Changes between Version 49 and Version 50 of Developer/Projects/SequencedInitialization

Timestamp:

06/15/10 16:26:24 (14 years ago)

Author:

Sh

Comment:

Order domain changes

Developer/Projects/SequencedInitialization

@@ -177 +177 @@
 there is no similar call like rtems_message_queue_creat which the application must call or 
 it will fail. So we must consider another method to solve this problem.
-=  Components Of Rtems Sequenced Initialization API  =
-
-
-# The rule of sort order
-
-# The definition of rtems Sysinit_Entry struct and its reference
-
-# The method of referencing the Sysinit_Entry struct
-
-; Rule of sort order
-
-We use a combination of three domains to define the order of initialization sequence, the three
-domains are {subsystem, order, index}. Every domain is an key word to sort. 
-
-Sort order API:
- /**
-  * @brief the first domain is subsystem
-  */
- #define SYSINIT_CLASS_API  0001
- /**
-  * @brief the second domain is order like before,nomal,after
-  */
- #define SYSINIT_ORDER_BEFORE    0
- #define SYSINIT_ORDER_NOMAL     1
- #define SYSINIT_ORDER_AFTER     2
- /**
-  * @brief the third domain is index
-  */
- #define SYSINIT_INDEX_FIRST    0000   /* first*/
- #define SYSINIT_INDEX_SECOND   0001   /* second*/
- #define SYSINIT_INDEX_THIRD    0002   /* third*/
- #define SYSINIT_INDEX_FOURTH   0003   /* fourth*/
- #define SYSINIT_INDEX_FIFTH    0004   /* fifth*/
- #define SYSINIT_INDEX_SIXTH    0005   /* sixth*/
- #define SYSINIT_INDEX_SEVENTH  0006   /* seventh*/
- #define SYSINIT_INDEX_EIGHTH   0007   /* eighth*/
- #define SYSINIT_INDEX_NINTH    0008   /* ninth*/
- #define SYSINIT_INDEX_TENTH    0009   /* tenth*/
- #define SYSINIT_INDEX_ELEVENTH  0010   /* eleventh*/
- #define SYSINIT_INDEX_TWELFTH   0011   /* twelfth */
-
-; The definition of rtems sysinit_core struct and its reference:
-
-The field of struct Sysinit_Entry will be extended in the futurn, now there is only one field filling in the struct. the field handler is the entry function of rtems sequenced initialization or termination.
+=  Components of the API  =
+
+
+We use a combination of three domains to define the order of initialization sequence, the two
+domains are (group, index). Every domain is an key word to sort. 
+
+The fields of Sysinit_Entry may be extended in the future, now there is only one field filling in the structure. The field handler is the entry function of RTEMS sequenced initialization or termination.
 
  /**
@@ -243 +206 @@
 
  #define SYSINIT_MAKE_ORDER(group, index) \
-   #group "." #index
- 
+   group "." index
+ 
+ #define SYSINIT_MAKE_INDEX(i3, i2, i1, i0) \
+   #i3 #i2 #i1 #i0
+ 
+ #define SYSINIT_INDEX_FIRST SYSINIT_MAKE_INDEX(0, 0, 0, 0)
+ #define SYSINIT_INDEX_MIDDLE SYSINIT_MAKE_INDEX(5, 0, 0, 0)
+ #define SYSINIT_INDEX_LAST SYSINIT_MAKE_INDEX(9, 9, 9, 9)
+ 
+ #define SYSINIT_GROUP_FIRST "0000"
+ #define SYSINIT_GROUP_EVENT "0110"
+ #define SYSINIT_GROUP_SEMAPHORE "0120"
+ #define SYSINIT_GROUP_LAST "9999"
+
  #define SYSINIT_ENTRY_NAME(handler) \
    _Sysinit_Entry_ ## handler
@@ -254 +229 @@
    extern const Sysinit_Entry SYSINIT_ENTRY_NAME(handler)
  
- #define SYSINIT_ENTRY(handler) \
+ #define SYSINIT_ENTRY(handler, group) \
    SYSINIT_DECLARE_ENTRY(handler); \
    const Sysinit_Entry SYSINIT_ENTRY_NAME(handler) \
-   __attribute__((section(".score.sysinit." SYSINIT_MAKE_ORDER(0, 0)))) \
+   __attribute__((section(".score.sysinit." SYSINIT_MAKE_ORDER(group, SYSINIT_INDEX_MIDDLE)))) \
    = { handler }
  
@@ -266 +241 @@
    = &SYSINIT_ENTRY_NAME(handler)
 
-; The method of referencing the Sysinit_Entry struct
-
 The implement of referencing the sequenced initialization struct. In the every C source code file include initialization function we define a sequenced initialization struct which contain the init function entry. And then a reference function point will be defined in the another file include a function which will be called if this object is used by application. For example
 ,consider the RTEMS Message API. In the RTEMS Message API's initialization call's source file we create a structure Sysinit_Entry include the field of the RTEMS Message API's initialization call entry. Then we reference this variable from the source file containing the rtems_message_queue_create code. Because the application must make a call to rtems_message_queue_create or all the other Message API calls will fail therefore this API needs only one reference from a single source file. But there is also a exception that if the application use RTEMS Event and RTEMS Signal API there is no similar call like rtems_message_queue_creat which the application must call or it will fail. '''So we must consider another method to solve this problem. Now we donot have a better way to fix it.'''