Mercurial > flash_v2
annotate packages/hal/common/current/include/pkgconf/hal.h @ 34:29bc183297e1 ecos-sw-1999-09-02
Merge from eCos master repository on 1999-09-02-16:26:10-BST
| author | jlarmour |
|---|---|
| date | Thu, 02 Sep 1999 16:11:22 +0000 |
| parents | 5af43b635655 |
| children | e97d78785e2d |
| rev | line source |
|---|---|
| 0 | 1 #ifndef CYGONCE_PKGCONF_HAL_H |
| 2 #define CYGONCE_PKGCONF_HAL_H | |
| 3 // ==================================================================== | |
| 4 // | |
| 2 | 5 // pkgconf/hal.h |
| 0 | 6 // |
| 2 | 7 // HAL configuration file |
| 0 | 8 // |
| 9 // ==================================================================== | |
| 10 //####COPYRIGHTBEGIN#### | |
| 11 // | |
| 12 // ------------------------------------------- | |
| 13 // The contents of this file are subject to the Cygnus eCos Public License | |
| 14 // Version 1.0 (the "License"); you may not use this file except in | |
| 15 // compliance with the License. You may obtain a copy of the License at | |
| 16 // http://sourceware.cygnus.com/ecos | |
| 17 // | |
| 18 // Software distributed under the License is distributed on an "AS IS" | |
| 19 // basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the | |
| 20 // License for the specific language governing rights and limitations under | |
| 21 // the License. | |
| 22 // | |
| 23 // The Original Code is eCos - Embedded Cygnus Operating System, released | |
| 24 // September 30, 1998. | |
| 25 // | |
| 26 // The Initial Developer of the Original Code is Cygnus. Portions created | |
| 2 | 27 // by Cygnus are Copyright (C) 1998,1999 Cygnus Solutions. All Rights Reserved. |
| 0 | 28 // ------------------------------------------- |
| 29 // | |
| 30 //####COPYRIGHTEND#### | |
| 31 // ==================================================================== | |
| 32 //#####DESCRIPTIONBEGIN#### | |
| 33 // | |
| 2 | 34 // Author(s): nickg, jskov |
| 35 // Contributors: nickg, jskov, | |
| 36 // jlarmour | |
| 37 // Date: 1999-01-21 | |
| 38 // Purpose: To allow the user to edit HAL configuration options. | |
| 0 | 39 // Description: |
| 40 // | |
| 41 //####DESCRIPTIONEND#### | |
| 42 // | |
| 43 // ==================================================================== | |
| 44 | |
| 45 /* --------------------------------------------------------------------- | |
| 46 * Some of the HAL configuration options depend on global options, | |
| 47 * so it is necessary to include the global options first. | |
| 48 */ | |
| 49 | |
| 50 #include <pkgconf/system.h> | |
| 51 | |
| 52 /* --------------------------------------------------------------------- | |
| 53 Define an overall package for the HAL. All other HAL packages | |
| 54 live below this. | |
| 55 | |
| 56 {{CFG_DATA | |
| 57 | |
| 58 cdl_package CYGPKG_HAL { | |
| 59 display "eCos HAL" | |
| 60 type dummy | |
| 61 description " | |
| 62 The eCos HAL package provide a porting layer for | |
| 63 higher-level parts of the system such as the kernel and the | |
| 64 C library. Each installation should have HAL packages for | |
| 65 one or more architectures, and for each architecture there | |
| 66 may be one or more supported platforms. It is necessary to | |
| 67 select one target architecture and one platform for that | |
| 68 architecture. There are also a number of configuration | |
| 69 options that are common to all HAL packages." | |
| 2 | 70 doc ref/ecos-ref/the-ecos-hardware-abstraction-layer-hal.html |
| 0 | 71 } |
| 72 | |
| 73 }}CFG_DATA */ | |
| 74 | |
| 75 /* --------------------------------------------------------------------- | |
| 76 * The platform-independent HAL configuration options go here, | |
| 77 * inside a component CYGPKG_HAL_COMMON. In practice some of the | |
| 78 * options are not completely platform-independent, but they are | |
| 79 * likely to be available on the vast majority of platforms and | |
| 80 * it is more convenient to provide them by default and let the | |
| 81 * appropriate platforms disable them (probably via a suitable | |
| 82 * interface). | |
| 83 * | |
| 84 * The common component is subdivided into components for | |
| 85 * interrupt handling, thread context, and rom monitor/gdb support. | |
| 86 | |
| 87 {{CFG_DATA | |
| 88 | |
| 89 cdl_component CYGPKG_HAL_COMMON { | |
| 90 display "Platform-independent HAL options" | |
| 91 parent CYGPKG_HAL | |
| 92 type dummy | |
| 93 description " | |
| 94 A number of configuration options are common to most or all | |
| 95 HAL packages, for example options controlling how much state | |
| 96 should be saved during a context switch. The implementations | |
| 97 of these options will vary from architecture to architecture." | |
| 98 } | |
| 99 | |
| 100 cdl_option CYGFUN_HAL_COMMON_KERNEL_SUPPORT { | |
| 101 display "Provide eCos kernel support" | |
| 102 parent CYGPKG_HAL_COMMON | |
| 103 requires CYGPKG_KERNEL | |
| 104 description " | |
| 105 The HAL can be configured to either support the full eCos | |
| 106 kernel, or to support only very simple applications which do | |
| 107 not require a full kernel. If kernel support is not required | |
| 108 then some of the startup, exception, and interrupt handling | |
| 109 code can be eliminated." | |
| 110 } | |
| 111 | |
| 112 }}CFG_DATA */ | |
| 113 #define CYGFUN_HAL_COMMON_KERNEL_SUPPORT | |
| 114 | |
| 115 /* {{CFG_DATA | |
| 116 | |
| 117 cdl_component CYGPKG_HAL_COMMON_INTERRUPTS { | |
| 118 display "HAL interrupt handling" | |
| 119 parent CYGPKG_HAL_COMMON | |
| 120 type dummy | |
| 121 description " | |
| 122 A number of configuration options related to interrupt | |
| 123 handling are common to most or all HAL packages, even though | |
| 124 the implementations will vary from architecture to | |
| 125 architecture." | |
| 126 } | |
| 127 | |
| 128 cdl_option CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK { | |
| 129 display "Use separate stack for interrupts" | |
| 130 parent CYGPKG_HAL_COMMON_INTERRUPTS | |
| 131 description " | |
| 132 When an interrupt occurs this interrupt can be handled either | |
| 133 on the current stack or on a separate stack maintained by the | |
| 134 HAL. Using a separate stack requires a small number of extra | |
| 135 instructions in the interrupt handling code, but it has the | |
| 136 advantage that it is no longer necessary to allow extra space | |
| 137 in every thread stack for the interrupt handlers. The amount | |
| 138 of extra space required depends on the interrupt handlers | |
| 139 that are being used." | |
| 140 } | |
| 141 | |
| 142 # NOTE: various parts of the system such as device drivers should | |
| 143 # impose lower bounds on this. The actual lower bound depends on a | |
| 144 # platform-specific value for startup overheads, and the minimum | |
| 145 # sizes specified by the various device drivers. If interrupts are | |
| 146 # not handled on a separate stack then only the startup overheads | |
| 147 # are significant. If nested interrupts are disabled then the | |
| 148 # lower bound is the maximum of the individual sizes, otherwise | |
| 149 # it is the sum of these sizes. It is not currently possible to | |
| 150 # express a relationship like this. | |
| 151 cdl_option CYGNUM_HAL_COMMON_INTERRUPTS_STACK_SIZE { | |
| 152 display "Interrupt stack size" | |
| 153 parent CYGPKG_HAL_COMMON_INTERRUPTS | |
| 154 type count | |
| 155 legal_values 1024 to 1048576 | |
| 156 description " | |
| 157 This configuration option specifies the stack size in bytes | |
| 158 for the interrupt stack. Typically this should be a multiple | |
| 159 of 16, but the exact requirements will vary from architecture | |
| 160 to architecture. The interrupt stack serves two separate | |
| 161 purposes. It is used as the stack during system | |
| 162 initialization. In addition, if the interrupt system is | |
| 163 configured to use a separate stack then all interrupts will | |
| 164 be processed on this stack. The exact memory requirements | |
| 165 will vary from application to application, and will depend | |
| 166 heavily on whether or not other interrupt-related options, | |
| 167 for example nested interrupts, are enabled." | |
| 168 } | |
| 169 | |
| 170 cdl_option CYGSEM_HAL_COMMON_INTERRUPTS_ALLOW_NESTING { | |
| 171 display "Allow nested interrupts" | |
| 172 parent CYGPKG_HAL_COMMON_INTERRUPTS | |
| 173 description " | |
| 174 When an interrupt occurs the HAL interrupt handling code can | |
| 175 either leave interrupts disabled for the duration of the | |
| 176 interrupt handling code, or by doing some extra work it can | |
| 177 reenable interrupts before invoking the interrupt handler and | |
| 178 thus allow nested interrupts to happen. If all the interrupt | |
| 179 handlers being used are small and do not involve any loops | |
| 180 then it is usually better to disallow nested interrupts. | |
| 181 However if any of the interrupt handlers are more complicated | |
| 182 than nested interrupts will usually be required." | |
| 183 } | |
| 184 | |
| 185 cdl_option CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT { | |
| 186 display "Save minimum context on interrupt" | |
| 187 parent CYGPKG_HAL_COMMON_INTERRUPTS | |
| 188 description " | |
| 189 The HAL interrupt handling code can exploit the calling conventions | |
| 190 defined for a given architecture to reduce the amount of state | |
| 191 that has to be saved. Generally this improves performance and | |
| 192 reduces code size. However it can make source-level debugging | |
| 193 more difficult. | |
| 194 " | |
| 195 } | |
| 196 | |
| 197 cdl_option CYGIMP_HAL_COMMON_INTERRUPTS_CHAIN { | |
| 198 display "Chain all interrupts together" | |
| 199 parent CYGPKG_HAL_COMMON_INTERRUPTS | |
| 200 description " | |
| 201 Interrupts can be attached to vectors either singly, or be | |
| 202 chained together. The latter is necessary if there is no way | |
| 203 of discovering which device has interrupted without | |
| 204 inspecting the device itself. It can also reduce the amount | |
| 205 of RAM needed for interrupt decoding tables and code." | |
| 206 } | |
| 207 | |
| 208 }}CFG_DATA | |
| 209 | |
| 210 */ | |
| 211 | |
| 212 #define CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK | |
| 213 #define CYGNUM_HAL_COMMON_INTERRUPTS_STACK_SIZE 4096 | |
| 214 #undef CYGSEM_HAL_COMMON_INTERRUPTS_ALLOW_NESTING | |
| 215 #define CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT | |
| 216 #undef CYGIMP_HAL_COMMON_INTERRUPTS_CHAIN | |
| 217 | |
| 218 | |
| 219 /* {{CFG_DATA | |
| 220 | |
| 221 cdl_component CYGPKG_HAL_COMMON_CONTEXT { | |
| 222 display "HAL context switch support" | |
| 223 parent CYGPKG_HAL_COMMON | |
| 224 type dummy | |
| 225 description " | |
| 226 A number of configuration options related to thread contexts | |
| 227 are common to most or all HAL packages, even though the | |
| 228 implementations will vary from architecture to architecture." | |
| 229 } | |
| 230 | |
| 231 cdl_option CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM { | |
| 232 display "Use minimum thread context" | |
| 233 parent CYGPKG_HAL_COMMON_CONTEXT | |
| 234 description " | |
| 235 The thread context switch code can exploit the calling conventions | |
| 236 defined for a given architecture to reduce the amount of state | |
| 237 that has to be saved during a context switch. Generally this | |
| 238 improves performance and reduces code size. However it can make | |
| 239 source-level debugging more difficult." | |
| 240 } | |
| 241 | |
| 242 }}CFG_DATA */ | |
| 243 #define CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM | |
| 244 | |
| 245 /* {{CFG_DATA | |
| 246 | |
| 247 # NOTE: The requirement for kernel exception support is bogus in that | |
| 248 # the user can supply a deliver_exception function herself. In that | |
| 249 # case, however, it is easy to force the kernel option off while leaving | |
| 250 # this one on. Having the requirement prevents accidental invalid | |
| 251 # configurations of the kernel. | |
| 252 cdl_option CYGPKG_HAL_EXCEPTIONS { | |
| 253 display "HAL exception support" | |
| 254 parent CYGPKG_HAL_COMMON | |
| 255 requires CYGPKG_KERNEL_EXCEPTIONS | |
| 256 description " | |
| 257 When a processor exception occurs, for example an attempt to | |
| 258 execute an illegal instruction or to perform a divide by | |
| 259 zero, this exception may be handled in a number of different | |
| 260 ways. If the target system has gdb support then typically | |
| 261 the exception will be handled by gdb code. Otherwise if the | |
| 262 HAL exception support is enabled then the HAL will invoke a | |
| 263 routine deliver_exception(). Typically this routine will be | |
| 264 provided by the eCos kernel, but it is possible for | |
| 265 application code to provide its own implementation. If the | |
| 266 HAL exception support is not enabled and a processor | |
| 267 exception occurs then the behaviour of the system is | |
| 268 undefined. | |
| 269 " | |
| 270 } | |
| 271 | |
| 272 }}CFG_DATA */ | |
| 273 #define CYGPKG_HAL_EXCEPTIONS | |
| 274 | |
| 2 | 275 /* {{CFG_DATA |
| 276 | |
| 277 cdl_option CYGSEM_HAL_STOP_CONSTRUCTORS_ON_FLAG { | |
| 278 display "Stop calling constructors early" | |
| 279 description "This option supports environments where some constructors | |
| 280 must be run in the context of a thread rather than at | |
| 281 simple system startup time. A boolean flag named | |
| 282 cyg_hal_stop_constructors is set to 1 when constructors | |
| 283 should no longer be invoked. It is up to some other | |
| 284 package to deal with the rest of the constructors. | |
| 285 In the current version this is only possible with the | |
| 286 C library." | |
| 287 type boolean | |
| 288 requires CYGSEM_LIBC_INVOKE_DEFAULT_STATIC_CONSTRUCTORS | |
| 289 parent CYGPKG_HAL_COMMON | |
| 290 } | |
| 291 | |
| 292 }}CFG_DATA */ | |
| 293 | |
| 294 #undef CYGSEM_HAL_STOP_CONSTRUCTORS_ON_FLAG | |
| 0 | 295 |
| 296 /* --------------------------------------------------------------------- | |
| 297 * Options related to source-level debugging and diagnostics. | |
| 298 | |
| 299 {{CFG_DATA | |
| 300 | |
| 301 cdl_component CYGPKG_HAL_DEBUG { | |
| 302 display "Source-level debugging support" | |
| 303 type dummy | |
| 304 parent CYGPKG_HAL | |
| 305 description " | |
| 306 If the source level debugger gdb is to be used for debugging | |
| 307 application code then it may be necessary to configure in support | |
| 308 for this in the HAL." | |
| 309 } | |
| 310 | |
| 311 cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS { | |
| 312 display "Include GDB stubs in HAL" | |
| 313 parent CYGPKG_HAL_DEBUG | |
| 314 requires !CYGPKG_HAL_POWERPC_SIM | |
| 315 requires !CYGPKG_HAL_MN10300_SIM | |
|
6
d376b777e2ce
Merge from eCos master repository on 1999-05-14-19:27:43-BST
jlarmour
parents:
2
diff
changeset
|
316 requires !CYGPKG_HAL_MIPS_SIM |
| 2 | 317 requires !CYGPKG_HAL_I386_LINUX |
| 318 requires !CYGPKG_HAL_SPARCLITE | |
| 0 | 319 description " |
| 320 This option causes a set of GDB stubs to be included into the | |
| 321 system. On some target systems the GDB support will be | |
| 322 provided by other means, for example by a ROM monitor. On | |
| 323 other targets, especially when building a ROM-booting system, | |
| 324 the necessary support has to go into the target library | |
| 325 itself." | |
| 326 } | |
| 327 | |
| 2 | 328 cdl_option CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT { |
|
18
7253dcc42a09
Merge from eCos master repository on 1999-06-25-15:31:50-BST
jlarmour
parents:
16
diff
changeset
|
329 display "Include GDB external break support for stubs" |
|
20
5f5102441818
Merge from eCos master repository on 1999-07-02-23:17:07-BST
jlarmour
parents:
18
diff
changeset
|
330 parent CYGPKG_HAL_DEBUG |
| 2 | 331 requires CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS |
|
6
d376b777e2ce
Merge from eCos master repository on 1999-05-14-19:27:43-BST
jlarmour
parents:
2
diff
changeset
|
332 requires !CYGPKG_HAL_MIPS_TX39_JMR3904 |
| 2 | 333 requires !CYGPKG_HAL_POWERPC_FADS |
|
16
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
334 requires !CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT |
| 2 | 335 description " |
| 336 This option causes the GDB stub to add a serial interrupt handler | |
| 337 which will listen for GDB break packets. This lets you stop the | |
| 338 target asynchronously when using GDB, usually by hitting Control+C | |
|
18
7253dcc42a09
Merge from eCos master repository on 1999-06-25-15:31:50-BST
jlarmour
parents:
16
diff
changeset
|
339 or pressing the STOP button. This option differs from |
|
7253dcc42a09
Merge from eCos master repository on 1999-06-25-15:31:50-BST
jlarmour
parents:
16
diff
changeset
|
340 CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT in that it is used when |
|
7253dcc42a09
Merge from eCos master repository on 1999-06-25-15:31:50-BST
jlarmour
parents:
16
diff
changeset
|
341 GDB stubs are present." |
| 2 | 342 } |
| 343 | |
|
16
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
344 cdl_option CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT { |
|
18
7253dcc42a09
Merge from eCos master repository on 1999-06-25-15:31:50-BST
jlarmour
parents:
16
diff
changeset
|
345 display "Include GDB external break support when no stubs" |
|
16
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
346 parent CYGPKG_HAL_DEBUG |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
347 requires !CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
348 description " |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
349 This option adds an interrupt handler for the GDB serial line |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
350 which will listen for GDB break packets. This lets you stop the |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
351 target asynchronously when using GDB, usually by hitting Control+C |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
352 or pressing the STOP button. This option differs from |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
353 CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT in that it is used when the GDB |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
354 stubs are NOT present." |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
355 } |
|
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
356 |
| 0 | 357 cdl_option CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT { |
| 358 display "Include GDB multi-threading debug support" | |
| 359 parent CYGPKG_HAL_DEBUG | |
| 360 requires CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT | |
| 361 description " | |
| 362 This option enables some extra HAL code which is needed | |
| 363 to support multi-threaded source level debugging." | |
| 364 } | |
| 365 | |
| 366 }}CFG_DATA */ | |
| 367 | |
| 2 | 368 #undef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS |
| 369 #undef CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT | |
|
16
4f2df4ab82c8
Merge from eCos master repository on 1999-06-18-15:25:04-BST
jlarmour
parents:
10
diff
changeset
|
370 #define CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT |
| 0 | 371 #define CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT |
| 372 | |
| 373 /* | |
| 374 * NOTE: | |
| 375 * | |
| 376 * Right now there is no easy way to express the ROM monitor options | |
| 377 * in CDL. The problem is that the default values depend on the | |
| 378 * target platform and on the desired start-up. It is possible to | |
| 379 * produce something that will work correctly in a clean world, but | |
| 380 * not something more general. | |
| 381 * | |
| 382 * One possibility is to duplicate the relevant options in the various | |
| 383 * platform HAL packages, renaming them to avoid collisions. This appears | |
| 384 * to be feasible with the current sources because the rom monitor options | |
| 385 * are only referenced in the HAL packages. It is not clear whether or not | |
| 386 * this will continue to be the case. */ | |
| 387 | |
| 388 /* | |
| 389 * Some development boards come with a ROM monitor that provides | |
| 390 * download and debug facilities. Such ROMs may also supply interrupt | |
| 391 * redirection and IO facilities. The following option causes the HAL | |
| 392 * to integrate with the ROM monitor present on the configured | |
| 393 * platform. If this option is not defined, the monitor will not be | |
| 394 * used. Where there is more than one ROM monitor for a specific | |
| 395 * platform, a subsidiary define should identify the appropriate monitor | |
| 396 * type. | |
| 397 */ | |
| 398 | |
| 399 //#define CYG_HAL_USE_ROM_MONITOR | |
| 400 | |
|
6
d376b777e2ce
Merge from eCos master repository on 1999-05-14-19:27:43-BST
jlarmour
parents:
2
diff
changeset
|
401 #if defined(CYG_HAL_MIPS_TX39_JMR3904) && defined(CYG_HAL_STARTUP_RAM) |
| 0 | 402 #define CYG_HAL_USE_ROM_MONITOR |
| 403 #define CYG_HAL_USE_ROM_MONITOR_CYGMON | |
| 404 #endif | |
|
30
641b639be825
Merge from eCos master repository on 1999-08-16-22:01:37-BST
jlarmour
parents:
20
diff
changeset
|
405 #if defined(CYG_HAL_MN10300_AM31_STDEVAL1) && defined(CYG_HAL_STARTUP_RAM) |
| 0 | 406 #define CYG_HAL_USE_ROM_MONITOR |
| 407 #define CYG_HAL_USE_ROM_MONITOR_CYGMON | |
| 408 #endif | |
| 409 | |
| 410 #ifdef CYG_HAL_USE_ROM_MONITOR | |
| 411 | |
| 412 //#define CYG_HAL_USE_ROM_MONITOR_SLOAD | |
| 413 //#define CYG_HAL_USE_ROM_MONITOR_GDB_STUBS | |
| 414 //#define CYG_HAL_USE_ROM_MONITOR_CYGMON | |
|
6
d376b777e2ce
Merge from eCos master repository on 1999-05-14-19:27:43-BST
jlarmour
parents:
2
diff
changeset
|
415 //#define CYG_HAL_USE_ROM_MONITOR_PMON |
| 0 | 416 |
| 417 #endif | |
| 418 | |
| 419 /* --------------------------------------------------------------------- | |
|
10
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
420 * This option decides whether we are going to BE a ROM monitor. On |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
421 * some targets and platforms we provide a simple ROM monitor (the GDB |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
422 * STUBS monitor) by means of a simple configuration of the HAL and |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
423 * GDB stubs. |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
424 * This option has no CDL since it is only set by a special configuration |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
425 * permutation used for building a monitor. |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
426 */ |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
427 |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
428 #undef CYG_HAL_ROM_MONITOR |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
429 |
|
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
430 /* --------------------------------------------------------------------- |
| 0 | 431 * |
| 432 * The section below deals with some inferences about package/feature | |
| 433 * presence that are not yet supported by the full external configuration | |
| 434 * tool; they are NOT user configuration, and you should NOT edit them. | |
| 435 */ | |
| 436 | |
| 437 /* | |
| 438 * CYG_HAL_<TARGET> and CYG_HAL_<TARGET>_<PLATFORM> are generated by | |
| 439 * pkgconf, using the information from the targets file. | |
| 440 * | |
| 441 * NOTE: Currently the code also needs these #defines. | |
| 442 */ | |
| 443 #ifdef CYG_HAL_POWERPC_COGENT | |
| 2 | 444 # define CYG_HAL_POWERPC_MPC8xx |
| 445 # define CYG_HAL_POWERPC_MPC860 | |
| 446 # undef CYG_HAL_POWERPC_MPC850 | |
| 447 # undef CYG_HAL_POWERPC_MPC823 | |
| 448 #endif | |
| 449 #ifdef CYG_HAL_POWERPC_FADS | |
| 450 # define CYG_HAL_POWERPC_MPC8xx | |
| 451 # define CYG_HAL_POWERPC_MPC860 | |
| 0 | 452 #endif |
|
32
5af43b635655
Merge from eCos master repository on 1999-08-18-15:20:01-BST
jlarmour
parents:
30
diff
changeset
|
453 #ifdef CYG_HAL_POWERPC_MBX |
|
5af43b635655
Merge from eCos master repository on 1999-08-18-15:20:01-BST
jlarmour
parents:
30
diff
changeset
|
454 # define CYG_HAL_POWERPC_MPC8xx |
|
5af43b635655
Merge from eCos master repository on 1999-08-18-15:20:01-BST
jlarmour
parents:
30
diff
changeset
|
455 # define CYG_HAL_POWERPC_MPC860 |
|
5af43b635655
Merge from eCos master repository on 1999-08-18-15:20:01-BST
jlarmour
parents:
30
diff
changeset
|
456 # define CYG_HAL_POWERPC_COPY_VECTORS |
|
5af43b635655
Merge from eCos master repository on 1999-08-18-15:20:01-BST
jlarmour
parents:
30
diff
changeset
|
457 #endif |
| 0 | 458 #ifdef CYG_HAL_POWERPC_SIM |
| 2 | 459 # define CYG_HAL_POWERPC_MPC603 |
| 0 | 460 #endif |
| 461 | |
|
10
d3fbcdfa1b2f
Merge from eCos master repository on 1999-05-29-00:13:11-BST
jlarmour
parents:
6
diff
changeset
|
462 |
|
6
d376b777e2ce
Merge from eCos master repository on 1999-05-14-19:27:43-BST
jlarmour
parents:
2
diff
changeset
|
463 #include CYGBLD_HAL_TARGET_H |
|
34
29bc183297e1
Merge from eCos master repository on 1999-09-02-16:26:10-BST
jlarmour
parents:
32
diff
changeset
|
464 #include CYGBLD_HAL_PLATFORM_H |
| 0 | 465 |
| 466 /* -------------------------------------------------------------------*/ | |
| 467 #endif /* CYGONCE_PKGCONF_HAL_H */ | |
| 468 /* EOF hal.h */ |