1 |
27 |
unneback |
# ====================================================================
|
2 |
|
|
#
|
3 |
|
|
# common.cdl
|
4 |
|
|
#
|
5 |
|
|
# HAL common configuration data
|
6 |
|
|
#
|
7 |
|
|
# ====================================================================
|
8 |
|
|
#####ECOSGPLCOPYRIGHTBEGIN####
|
9 |
|
|
## -------------------------------------------
|
10 |
|
|
## This file is part of eCos, the Embedded Configurable Operating System.
|
11 |
|
|
## Copyright (C) 1998, 1999, 2000, 2001, 2002 Red Hat, Inc.
|
12 |
|
|
##
|
13 |
|
|
## eCos is free software; you can redistribute it and/or modify it under
|
14 |
|
|
## the terms of the GNU General Public License as published by the Free
|
15 |
|
|
## Software Foundation; either version 2 or (at your option) any later version.
|
16 |
|
|
##
|
17 |
|
|
## eCos is distributed in the hope that it will be useful, but WITHOUT ANY
|
18 |
|
|
## WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
19 |
|
|
## FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
|
20 |
|
|
## for more details.
|
21 |
|
|
##
|
22 |
|
|
## You should have received a copy of the GNU General Public License along
|
23 |
|
|
## with eCos; if not, write to the Free Software Foundation, Inc.,
|
24 |
|
|
## 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
|
25 |
|
|
##
|
26 |
|
|
## As a special exception, if other files instantiate templates or use macros
|
27 |
|
|
## or inline functions from this file, or you compile this file and link it
|
28 |
|
|
## with other works to produce a work based on this file, this file does not
|
29 |
|
|
## by itself cause the resulting work to be covered by the GNU General Public
|
30 |
|
|
## License. However the source code for this file must still be made available
|
31 |
|
|
## in accordance with section (3) of the GNU General Public License.
|
32 |
|
|
##
|
33 |
|
|
## This exception does not invalidate any other reasons why a work based on
|
34 |
|
|
## this file might be covered by the GNU General Public License.
|
35 |
|
|
##
|
36 |
|
|
## Alternative licenses for eCos may be arranged by contacting Red Hat, Inc.
|
37 |
|
|
## at http://sources.redhat.com/ecos/ecos-license/
|
38 |
|
|
## -------------------------------------------
|
39 |
|
|
#####ECOSGPLCOPYRIGHTEND####
|
40 |
|
|
# ====================================================================
|
41 |
|
|
######DESCRIPTIONBEGIN####
|
42 |
|
|
#
|
43 |
|
|
# Author(s): jskov
|
44 |
|
|
# Original data: nickg,jskov,jlarmour
|
45 |
|
|
# Contributors:
|
46 |
|
|
# Date: 1999-07-02
|
47 |
|
|
#
|
48 |
|
|
#####DESCRIPTIONEND####
|
49 |
|
|
#
|
50 |
|
|
# ====================================================================
|
51 |
|
|
|
52 |
|
|
cdl_option CYGFUN_HAL_COMMON_KERNEL_SUPPORT {
|
53 |
|
|
display "Provide eCos kernel support"
|
54 |
|
|
requires CYGPKG_KERNEL
|
55 |
|
|
default_value CYGPKG_KERNEL
|
56 |
|
|
description "
|
57 |
|
|
The HAL can be configured to either support the full eCos
|
58 |
|
|
kernel, or to support only very simple applications which do
|
59 |
|
|
not require a full kernel. If kernel support is not required
|
60 |
|
|
then some of the startup, exception, and interrupt handling
|
61 |
|
|
code can be eliminated."
|
62 |
|
|
}
|
63 |
|
|
|
64 |
|
|
# NOTE: The requirement for kernel exception support is bogus in that
|
65 |
|
|
# the user can supply a deliver_exception function herself. In that
|
66 |
|
|
# case, however, it is easy to force the kernel option off while leaving
|
67 |
|
|
# this one on. Having the requirement prevents accidental invalid
|
68 |
|
|
# configurations of the kernel.
|
69 |
|
|
cdl_option CYGPKG_HAL_EXCEPTIONS {
|
70 |
|
|
display "HAL exception support"
|
71 |
|
|
requires CYGPKG_KERNEL_EXCEPTIONS
|
72 |
|
|
default_value CYGPKG_KERNEL_EXCEPTIONS
|
73 |
|
|
description "
|
74 |
|
|
When a processor exception occurs, for example an attempt to
|
75 |
|
|
execute an illegal instruction or to perform a divide by
|
76 |
|
|
zero, this exception may be handled in a number of different
|
77 |
|
|
ways. If the target system has gdb support then typically
|
78 |
|
|
the exception will be handled by gdb code. Otherwise if the
|
79 |
|
|
HAL exception support is enabled then the HAL will invoke a
|
80 |
|
|
routine deliver_exception(). Typically this routine will be
|
81 |
|
|
provided by the eCos kernel, but it is possible for
|
82 |
|
|
application code to provide its own implementation. If the
|
83 |
|
|
HAL exception support is not enabled and a processor
|
84 |
|
|
exception occurs then the behaviour of the system is
|
85 |
|
|
undefined."
|
86 |
|
|
}
|
87 |
|
|
|
88 |
|
|
cdl_option CYGSEM_HAL_STOP_CONSTRUCTORS_ON_FLAG {
|
89 |
|
|
display "Stop calling constructors early"
|
90 |
|
|
requires CYGSEM_LIBC_INVOKE_DEFAULT_STATIC_CONSTRUCTORS
|
91 |
|
|
default_value 0
|
92 |
|
|
description "
|
93 |
|
|
This option supports environments where some constructors
|
94 |
|
|
must be run in the context of a thread rather than at
|
95 |
|
|
simple system startup time. A boolean flag named
|
96 |
|
|
cyg_hal_stop_constructors is set to 1 when constructors
|
97 |
|
|
should no longer be invoked. It is up to some other
|
98 |
|
|
package to deal with the rest of the constructors.
|
99 |
|
|
In the current version this is only possible with the
|
100 |
|
|
C library."
|
101 |
|
|
}
|
102 |
|
|
|
103 |
|
|
cdl_interface CYGINT_HAL_SUPPORTS_MMU_TABLES {
|
104 |
|
|
display "HAL uses the MMU and allows for CDL manipulation of it's use"
|
105 |
|
|
}
|
106 |
|
|
|
107 |
|
|
cdl_option CYGSEM_HAL_INSTALL_MMU_TABLES {
|
108 |
|
|
display "Install MMU tables."
|
109 |
|
|
default_value { CYG_HAL_STARTUP != "RAM" }
|
110 |
|
|
active_if CYGINT_HAL_SUPPORTS_MMU_TABLES
|
111 |
|
|
description "This option controls whether this application installs
|
112 |
|
|
its own Memory Management Unit (MMU) tables, or relies on the
|
113 |
|
|
existing environment to run."
|
114 |
|
|
}
|
115 |
|
|
|
116 |
|
|
cdl_option CYGSEM_HAL_STATIC_MMU_TABLES {
|
117 |
|
|
display "Use static MMU tables."
|
118 |
|
|
default_value 0
|
119 |
|
|
requires CYGSEM_HAL_INSTALL_MMU_TABLES
|
120 |
|
|
description "This option defines an environment where any Memory
|
121 |
|
|
Management Unit (MMU) tables are constant. Normally used by ROM
|
122 |
|
|
based environments, this provides a way to save RAM usage which
|
123 |
|
|
would otherwise be required for these tables."
|
124 |
|
|
}
|
125 |
|
|
|
126 |
|
|
cdl_component CYGDBG_HAL_DIAG_TO_DEBUG_CHAN {
|
127 |
|
|
display "Route diagnostic output to debug channel"
|
128 |
|
|
default_value { (CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS \
|
129 |
|
|
|| CYG_HAL_STARTUP == "RAM") ? 1 : 0}
|
130 |
|
|
active_if !CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
|
131 |
|
|
active_if { CYGPKG_HAL_ARM || CYGPKG_HAL_POWERPC_MPC8xx \
|
132 |
|
|
|| CYGPKG_HAL_V85X_V850 || CYGSEM_HAL_VIRTUAL_VECTOR_DIAG }
|
133 |
|
|
description "
|
134 |
|
|
If not inheriting the console setup from the ROM monitor,
|
135 |
|
|
it is possible to redirect diagnostic output to the debug
|
136 |
|
|
channel by enabling this option. Depending on the debugger
|
137 |
|
|
used it may also be necessary to select a mangler for the
|
138 |
|
|
output to be displayed by the debugger."
|
139 |
|
|
|
140 |
|
|
cdl_option CYGSEM_HAL_DIAG_MANGLER {
|
141 |
|
|
display "Mangler used on diag output"
|
142 |
|
|
flavor data
|
143 |
|
|
legal_values {"GDB" "None"}
|
144 |
|
|
default_value { "GDB" }
|
145 |
|
|
description "
|
146 |
|
|
It is sometimes necessary to mangle (encode) the
|
147 |
|
|
diag ASCII text output in order for it to show up at the
|
148 |
|
|
other end. In particular, GDB may silently ignore raw
|
149 |
|
|
ASCII text."
|
150 |
|
|
}
|
151 |
|
|
}
|
152 |
|
|
|