From 66c50e281a052374d1b7b2761a75f51d6d129be2 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Tue, 4 Dec 2007 22:18:30 +0000 Subject: 2007-12-04 Joel Sherrill * cpu_supplement/arm.t, cpu_supplement/i386.t, cpu_supplement/m68k.t, cpu_supplement/mips.t, cpu_supplement/powerpc.t, cpu_supplement/sh.t, cpu_supplement/sparc.t, cpu_supplement/tic4x.t, porting/cpuinit.t, user/conf.t, user/init.t: Move interrupt_stack_size field from CPU Table to Configuration Table. Eliminate CPU Table from all ports. Delete references to CPU Table in all forms. --- doc/porting/cpuinit.t | 98 --------------------------------------------------- 1 file changed, 98 deletions(-) (limited to 'doc/porting') diff --git a/doc/porting/cpuinit.t b/doc/porting/cpuinit.t index 1fdf3e3712..d396be22a9 100644 --- a/doc/porting/cpuinit.t +++ b/doc/porting/cpuinit.t @@ -16,101 +16,12 @@ as it pertains to the CPU dependent code. XXX general startup sequence description rewritten to make it more applicable to CPU depdent code in executive -@section CPU Dependent Configuration Table - -The CPU Dependent Configuration Table contains information which tailors -the behavior of RTEMS base Some of the fields in this table are required -to be present in all ports of RTEMS. These fields appear at the beginning -of the data structure. Fields past this point may be CPU family and CPU -model dependent. For example, a port may add a field to specify the -default value for an interrupt mask register on the CPU. This table is -initialized by the Board Support Package and passed to the -rtems_initialize_executive or rtems_initialize_executive_early directive. - -@example -typedef struct @{ - void (*pretasking_hook)( void ); - void (*predriver_hook)( void ); - void (*postdriver_hook)( void ); - void (*idle_task)( void ); - boolean do_zero_of_workspace; - unsigned32 idle_task_stack_size; - unsigned32 interrupt_stack_size; - unsigned32 extra_mpci_receive_server_stack; - void * (*stack_allocate_hook)( unsigned32 ); - void (*stack_free_hook)( void* ); - /* end of fields required on all CPUs */ - - unsigned32 some_other_cpu_dependent_info; -@} rtems_cpu_table; -@end example - -@table @code -@item pretasking_hook -is the address of the user provided routine which is invoked -once RTEMS APIs are initialized. This routine will be invoked -before any system tasks are created. Interrupts are disabled. -This field may be NULL to indicate that the hook is not utilized. - -@item predriver_hook -is the address of the user provided -routine that is invoked immediately before the -the device drivers and MPCI are initialized. RTEMS -initialization is complete but interrupts and tasking are disabled. -This field may be NULL to indicate that the hook is not utilized. - -@item postdriver_hook -is the address of the user provided -routine that is invoked immediately after the -the device drivers and MPCI are initialized. RTEMS -initialization is complete but interrupts and tasking are disabled. -This field may be NULL to indicate that the hook is not utilized. - -@item idle_task -is the address of the optional user -provided routine which is used as the system's IDLE task. If -this field is not NULL, then the RTEMS default IDLE task is not -used. This field may be NULL to indicate that the default IDLE -is to be used. - -@item do_zero_of_workspace -indicates whether RTEMS should -zero the Workspace as part of its initialization. If set to -TRUE, the Workspace is zeroed. Otherwise, it is not. - -@item idle_task_stack_size -is the size of the RTEMS idle task stack in bytes. -If this number is less than MINIMUM_STACK_SIZE, then the -idle task's stack will be MINIMUM_STACK_SIZE in byte. - -@item interrupt_stack_size -is the size of the RTEMS allocated interrupt stack in bytes. -This value must be at least as large as MINIMUM_STACK_SIZE. - -@item extra_mpci_receive_server_stack -is the extra stack space allocated for the RTEMS MPCI receive server task -in bytes. The MPCI receive server may invoke nearly all directives and -may require extra stack space on some targets. - -@item stack_allocate_hook -is the address of the optional user provided routine which allocates -memory for task stacks. If this hook is not NULL, then a stack_free_hook -must be provided as well. - -@item stack_free_hook -is the address of the optional user provided routine which frees -memory for task stacks. If this hook is not NULL, then a stack_allocate_hook -must be provided as well. - -@end table - @section Initializing the CPU The _CPU_Initialize routine performs processor dependent initialization. @example void _CPU_Initialize( - rtems_cpu_table *cpu_table, void (*thread_dispatch) /* may be ignored */ ) @end example @@ -139,12 +50,3 @@ FP context here and copy it to the task's during Context_Initialize. If this technique is used to initialize the FP contexts, then it is important to ensure that the state of the floating point unit is in a coherent, initialized state. - -Finally, this routine is responsible for copying the application's CPU -Table into a locally accessible and modifiable area. This is shown below: - -@example -_CPU_Table = *cpu_table; -@end example - - -- cgit v1.2.3