1 | @c |
---|
2 | @c COPYRIGHT (c) 1988-1997. |
---|
3 | @c On-Line Applications Research Corporation (OAR). |
---|
4 | @c All rights reserved. |
---|
5 | @c |
---|
6 | |
---|
7 | @ifinfo |
---|
8 | @node Processor Dependent Information Table, Processor Dependent Information Table Introduction, Board Support Packages Processor Initialization, Top |
---|
9 | @end ifinfo |
---|
10 | @chapter Processor Dependent Information Table |
---|
11 | @ifinfo |
---|
12 | @menu |
---|
13 | * Processor Dependent Information Table Introduction:: |
---|
14 | * Processor Dependent Information Table CPU Dependent Information Table:: |
---|
15 | @end menu |
---|
16 | @end ifinfo |
---|
17 | |
---|
18 | @ifinfo |
---|
19 | @node Processor Dependent Information Table Introduction, Processor Dependent Information Table CPU Dependent Information Table, Processor Dependent Information Table, Processor Dependent Information Table |
---|
20 | @end ifinfo |
---|
21 | @section Introduction |
---|
22 | |
---|
23 | Any highly processor dependent information required |
---|
24 | to describe a processor to RTEMS is provided in the CPU |
---|
25 | Dependent Information Table. This table is not required for all |
---|
26 | processors supported by RTEMS. This chapter describes the |
---|
27 | contents, if any, for a particular processor type. |
---|
28 | |
---|
29 | @ifinfo |
---|
30 | @node Processor Dependent Information Table CPU Dependent Information Table, Memory Requirements, Processor Dependent Information Table Introduction, Processor Dependent Information Table |
---|
31 | @end ifinfo |
---|
32 | @section CPU Dependent Information Table |
---|
33 | |
---|
34 | The PA-RISC version of the RTEMS CPU Dependent |
---|
35 | Information Table contains the information required to interface |
---|
36 | a Board Support Package and RTEMS on the PA-RISC. This |
---|
37 | information is provided to allow RTEMS to interoperate |
---|
38 | effectively with the BSP. The C structure definition is given |
---|
39 | here: |
---|
40 | |
---|
41 | @example |
---|
42 | typedef struct @{ |
---|
43 | void (*pretasking_hook)( void ); |
---|
44 | void (*predriver_hook)( void ); |
---|
45 | void (*postdriver_hook)( void ); |
---|
46 | void (*idle_task)( void ); |
---|
47 | boolean do_zero_of_workspace; |
---|
48 | unsigned32 interrupt_stack_size; |
---|
49 | unsigned32 extra_mpci_receive_server_stack; |
---|
50 | void * (*stack_allocate_hook)( unsigned32 ); |
---|
51 | void (*stack_free_hook)( void * ); |
---|
52 | /* end of fields required on all CPUs */ |
---|
53 | |
---|
54 | hppa_rtems_isr_entry spurious_handler; |
---|
55 | |
---|
56 | unsigned32 itimer_clicks_per_microsecond; /* for use by Clock driver */ |
---|
57 | @} rtems_cpu_table; |
---|
58 | @end example |
---|
59 | |
---|
60 | @table @code |
---|
61 | @item pretasking_hook |
---|
62 | is the address of the |
---|
63 | user provided routine which is invoked once RTEMS initialization |
---|
64 | is complete but before interrupts and tasking are enabled. This |
---|
65 | field may be NULL to indicate that the hook is not utilized. |
---|
66 | |
---|
67 | @item predriver_hook |
---|
68 | is the address of the user provided |
---|
69 | routine which is invoked with tasking enabled immediately before |
---|
70 | the MPCI and device drivers are initialized. RTEMS |
---|
71 | initialization is complete, interrupts and tasking are enabled, |
---|
72 | but no device drivers are initialized. This field may be NULL to |
---|
73 | indicate that the hook is not utilized. |
---|
74 | |
---|
75 | @item postdriver_hook |
---|
76 | is the address of the user provided |
---|
77 | routine which is invoked with tasking enabled immediately after |
---|
78 | the MPCI and device drivers are initialized. RTEMS |
---|
79 | initialization is complete, interrupts and tasking are enabled, |
---|
80 | and the device drivers are initialized. This field may be NULL |
---|
81 | to indicate that the hook is not utilized. |
---|
82 | |
---|
83 | @item idle_task |
---|
84 | is the address of the optional user |
---|
85 | provided routine which is used as the system's IDLE task. If |
---|
86 | this field is not NULL, then the RTEMS default IDLE task is not |
---|
87 | used. This field may be NULL to indicate that the default IDLE |
---|
88 | is to be used. |
---|
89 | |
---|
90 | @item do_zero_of_workspace |
---|
91 | indicates whether RTEMS should |
---|
92 | zero the Workspace as part of its initialization. If set to |
---|
93 | TRUE, the Workspace is zeroed. Otherwise, it is not. |
---|
94 | |
---|
95 | @item interrupt_stack_size |
---|
96 | is the size of the RTEMS allocated interrupt stack in bytes. |
---|
97 | This value must be at least as large as MINIMUM_STACK_SIZE. |
---|
98 | |
---|
99 | @item extra_mpci_receive_server_stack |
---|
100 | is the extra stack space allocated for the RTEMS MPCI receive server task |
---|
101 | in bytes. The MPCI receive server may invoke nearly all directives and |
---|
102 | may require extra stack space on some targets. |
---|
103 | |
---|
104 | @item stack_allocate_hook |
---|
105 | is the address of the optional user provided routine which allocates |
---|
106 | memory for task stacks. If this hook is not NULL, then a stack_free_hook |
---|
107 | must be provided as well. |
---|
108 | |
---|
109 | @item stack_free_hook |
---|
110 | is the address of the optional user provided routine which frees |
---|
111 | memory for task stacks. If this hook is not NULL, then a stack_allocate_hook |
---|
112 | must be provided as well. |
---|
113 | |
---|
114 | @item spurious_handler |
---|
115 | is the address of the optional user provided routine which is invoked |
---|
116 | when a spurious external interrupt occurs. A spurious interrupt is one |
---|
117 | for which no handler is installed. |
---|
118 | |
---|
119 | @item itimer_clicks_per_microsecond |
---|
120 | is the number of countdowns in the on-CPU timer which corresponds |
---|
121 | to a microsecond. This is a function of the clock speed of the CPU |
---|
122 | being used. |
---|
123 | |
---|
124 | @end table |
---|