Introduction
------------
The configuration database is collection of configuration options
organized in a tree structure:
+- Code maturity level options
| +- Prompt for development and/or incomplete code/drivers
+- General setup
| +- Networking support
| +- System V IPC
| +- BSD Process Accounting
| +- Sysctl support
+- Loadable module support
| +- Enable loadable module support
| +- Set version information on all module symbols
| +- Kernel module loader
+- ...
Every entry has its own dependencies. These dependencies are used
to determine the visibility of an entry. Any child entry is only
visible if its parent entry is also visible.
Menu entries
------------
Most entries define a config option, all other entries help to organize
them. A single configuration option is defined like this:
config MODVERSIONS
bool "Set version information on all module symbols"
depends MODULES
help
Usually, modules have to be recompiled whenever you switch to a new
kernel. ...
Every line starts with a key word and can be followed by multiple
arguments. "config" starts a new config entry. The following lines
define attributes for this config option. Attributes can be the type of
the config option, input prompt, dependencies, help text and default
values. A config option can be defined multiple times with the same
name, but every definition can have only a single input prompt and the
type must not conflict.
Menu attributes
---------------
A menu entry can have a number of attributes. Not all of them are
applicable everywhere (see syntax).
- type definition: "bool"/"tristate"/"string"/"hex"/"integer"
Every config option must have a type. There are only two basic types:
tristate and string, the other types are based on these two. The type
definition optionally accepts an input prompt, so these two examples
are equivalent:
bool "Networking support"
and
bool
prompt "Networking support"
- input prompt: "prompt" <prompt> ["if" <expr>]
Every menu entry can have at most one prompt, which is used to display
to the user. Optionally dependencies only for this prompt can be added
with "if".
- default value: "default" <expr> ["if" <expr>]
A config option can have any number of default values. If multiple
default values are visible, only the first defined one is active.
Default values are not limited to the menu entry, where they are
defined, this means the default can be defined somewhere else or be
overridden by an earlier definition.
The default value is only assigned to the config symbol if no other
value was set by the user (via the input prompt above). If an input
prompt is visible the default value is presented to the user and can
be overridden by him.
Optionally dependencies only for this default value can be added with
"if".
- dependencies: "depends on"/"requires" <expr>
This defines a dependency for this menu entry. If multiple
dependencies are defined they are connected with '&&'. Dependencies
are applied to all other options within this menu entry (which also
accept an "if" expression), so these two examples are equivalent:
bool "foo" if BAR
default y if BAR
and
depends on BAR
bool "foo"
default y
- reverse dependencies: "select" <symbol> ["if" <expr>]
While normal dependencies reduce the upper limit of a symbol (see
below), reverse dependencies can be used to force a lower limit of
another symbol. The value of the current menu symbol is used as the
minimal value <symbol> can be set to. If <symbol> is selected multiple
times, the limit is set to the largest selection.
Reverse dependencies can only be used with boolean or tristate
symbols.
- numerical ranges: "range" <symbol> <symbol> ["if" <expr>]
This allows to limit the range of possible input values for integer
and hex symbols. The user can only input a value which is larger than
or equal to the first symbol and smaller than or equal to the second
symbol.
- help text: "help" or "---help---"
This defines a help text. The end of the help text is determined by
the indentation level, this means it ends at the first line which has
a smaller indentation than the first line of the help text.
"---help---" and "help" do not differ in behaviour, "---help---" is
used to help visually seperate configuration logic from help within
the file as an aid to developers.
Menu dependencies
-----------------
Dependencies define the visibility of a menu entry and can also reduce
the input range of tristate symbols. The tristate logic used in the
expressions uses one more state than normal boolean logic to express the
module state. Dependency expressions have the following syntax:
<expr> ::= <symbol> (1)
<symbol> '=' <symbol> (2)
<symbol> '!=' <symbol> (3)
'(' <expr> ')' (4)
'!' <expr> (5)
<expr> '&&' <expr> (6)
<expr> '||' <expr> (7)
Expressions are listed in decreasing order of precedence.
(1) Convert the symbol into an expression. Boolean and tristate symbols
are simply converted into the respective expression values. All
other symbol types result in 'n'.
(2) If the values of both symbols are equal, it returns 'y',
otherwise 'n'.
(3) If the values of both symbols are equal, it returns 'n',
otherwise 'y'.
(4) Returns the value of the expression. Used to override precedence.
(5) Returns the result of (2-/expr/).
(6) Returns the result of max(/expr/, /expr/).
(7) Returns the result of min(/expr/, /expr/).
An expression can have a value of 'n', 'm' or 'y' (or 0, 1, 2
respectively for calculations). A menu entry becomes visible when it's
expression evaluates to 'm' or 'y'.
There are two types of symbols: constant and nonconstant symbols.
Nonconstant symbols are the most common ones and are defined with the
'config' statement. Nonconstant symbols consist entirely of alphanumeric
characters or underscores.
Constant symbols are only part of expressions. Constant symbols are
always surrounded by single or double quotes. Within the quote any
other character is allowed and the quotes can be escaped using '\'.
Menu structure
--------------
The position of a menu entry in the tree is determined in two ways. First
it can be specified explicitly:
menu "Network device support"
depends NET
config NETDEVICES
...
endmenu
All entries within the "menu" ... "endmenu" block become a submenu of
"Network device support". All subentries inherit the dependencies from
the menu entry, e.g. this means the dependency "NET" is added to the
dependency list of the config option NETDEVICES.
The other way to generate the menu structure is done by analyzing the
dependencies. If a menu entry somehow depends on the previous entry, it
can be made a submenu of it. First, the previous (parent) symbol must
be part of the dependency list and then one of these two conditions
must be true:
- the child entry must become invisible, if the parent is set to 'n'
- the child entry must only be visible, if the parent is visible
config MODULES
bool "Enable loadable module support"
config MODVERSIONS
bool "Set version information on all module symbols"
depends MODULES
comment "module support disabled"
depends !MODULES
MODVERSIONS directly depends on MODULES, this means it's only visible if
MODULES is different from 'n'. The comment on the other hand is always
visible when MODULES is visible (the (empty) dependency of MODULES is
also part of the comment dependencies).
Kconfig syntax
--------------
The configuration file describes a series of menu entries, where every
line starts with a keyword (except hel
没有合适的资源?快使用搜索试试~ 我知道了~
core_arm.tar.gz_arm processor vhdl_arm9 vh_core_arm_core_arm.tar
1.该资源内容由用户上传,如若侵权请联系客服进行举报
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
版权申诉
0 下载量 48 浏览量
2022-09-21
03:21:58
上传
评论
收藏 640KB GZ 举报
温馨提示
共365个文件
vhd:160个
c:39个
el:30个
用VHDL语言实现的ARM处理器的标准内核的源代码程序,可在重用
资源推荐
资源详情
资源评论
收起资源包目录
core_arm.tar.gz_arm processor vhdl_arm9 vh_core_arm_core_arm.tar (365个子文件)
Config.in.arch 1KB
arm 32KB
Config.arm 0B
lex.zconf.c 106KB
zconf.tab.c 59KB
tkgen.c 46KB
load.c 45KB
sparc.c 44KB
arm.c 37KB
expr.c 25KB
tkparse.c 19KB
mconf.c 17KB
symbol.c 16KB
textbox.c 16KB
tkcond.c 14KB
menubox.c 13KB
conf.c 11KB
bucomm.c 11KB
menu.c 10KB
util.c 10KB
checklist.c 10KB
confdata.c 8KB
mem.c 7KB
gendc.c 7KB
inputbox.c 6KB
filemode.c 6KB
args.c 4KB
genic.c 4KB
mctrl.c 3KB
yesno.c 3KB
Makefile.c 3KB
msgbox.c 3KB
io.c 2KB
apbmst.c 1KB
ahbarb.c 1KB
testcache.c 471B
sys.c 338B
out.c 196B
test.c 195B
io.c 130B
arg.c 67B
uart.c 6B
lex.zconf.c_shipped 106KB
zconf.tab.c_shipped 59KB
Makefile.clean 641B
Makefile.conf 642B
.config 3KB
Thumbs.db 15KB
dcache 15KB
Config.default 0B
Makefile.defs 2KB
.Makefile.dep 53KB
.dep 346B
arm.el 14KB
sparc.el 12KB
cdef.el 7KB
cdef_lib_g1.el 5KB
cdef_lib_i1.el 5KB
cdef_lib_pc.el 4KB
l1.el 2KB
cdef_lib_pv.el 2KB
c1.el 2KB
cdef_lib_b1.el 2KB
b1.el 2KB
cp1.el 2KB
g1.el 2KB
components.el 2KB
compressor.el 1KB
ppc.el 1KB
m68k.el 1KB
m1.el 1KB
cdef_lib_l1.el 1KB
c1.el 1KB
cdef_lib_c1.el 1KB
cdef_calc.el 854B
cdef_lib_h1.el 366B
h1.el 354B
cdef_lib_m1.el 315B
mult.el 301B
cla.el 195B
count.el 171B
arm_lib_enc.el 163B
c1.el 2B
docopen.gif 203B
docclose.gif 200B
close.gif 200B
stats_space.gif 55B
dialog.h 6KB
colors.h 5KB
expr.h 5KB
zconf.tab.h 3KB
lkc.h 3KB
config.h 3KB
tkparse.h 2KB
tmki.h 2KB
lkc_proto.h 2KB
lkc_defs.h 1KB
gendc.h 691B
mctrl.h 636B
genic.h 624B
共 365 条
- 1
- 2
- 3
- 4
资源评论
我虽横行却不霸道
- 粉丝: 75
- 资源: 1万+
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功