OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/Kconfig

34 lines
847 B
Plaintext
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
boards: Kconfig: rename BOARD_DEPRECATED to BOARD_DEPRECATED_RELEASE Renaming this Kconfig option given it corresponds to a version string for a particular release. Signed-off-by: Vincent Wan <vincent.wan@linaro.org>
2020-01-10 06:20:44 +08:00
config BOARD_DEPRECATED_RELEASE
build: add Kconfig mechanism for deprecating boards If a deprecated board is built, a warning is presented indicating what future release the board will be removed. Change-Id: Ib166198d8b71303b990a30f79429f51871591a97 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 04:05:35 +08:00
string
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 23:08:21 +08:00
This hidden option is set in the board configuration and indicates
the Zephyr release that the board configuration will be removed.
When set, any build for that board will generate a clearly visible
deprecation warning.
build: add Kconfig mechanism for deprecating boards If a deprecated board is built, a warning is presented indicating what future release the board will be removed. Change-Id: Ib166198d8b71303b990a30f79429f51871591a97 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 04:05:35 +08:00
boards: mark qemu targets with a unified Kconfig This will allow checking if we are building for QEMU globally, without having to know the exact architecture and board name. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:08:21 +08:00
config QEMU_TARGET
boards: Fix QEMU_TARGET config prompt and default The default boolean setting for QEMU_TARGET was incorrectly placed in the prompt field, so it was showing up as a config option in 'make menuconfig' when it should be hidden. Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-08-01 04:38:03 +08:00
bool
boards: mark qemu targets with a unified Kconfig This will allow checking if we are building for QEMU globally, without having to know the exact architecture and board name. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:08:21 +08:00
help
Mark all QEMU targets with this variable for checking whether we are
running in an emulated environment.
Kconfig: Rename $ENV_VAR_{ARCH,BOARD_DIR} to $ARCH/$BOARD_DIR The prefixes might be a leftover from the old 'option env="..."' symbols (which are no longer needed). Since environment variables can be referenced directly now, there's no point in having a prefix. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-09-05 18:58:05 +08:00
# Note: $BOARD_DIR might be a glob pattern
kconfig: Make 'source' non-globbing and use 'gsource' Until now, Zephyr has used a patched Kconfiglib that turns 'source' into a globbing source (by replacing 'source' with 'gsource' at the token level). There's two problems with this: - The patch needs to be maintained separately - Misspelled filenames are silently ignored, as they look like glob patterns that don't match anything Fix it as follows: 1. Replace all 'source' statements that use wildcards with 'gsource' 2. Remove the custom Kconfiglib patch so that 'source' no longer globs The sed pattern '/source.*[*?]/s/source/gsource/' was run over all Kconfig* files to do the replacement. source's that use environment variables that might contain glob patterns were manually changed to gsource. Building the docs in doc/ is a good test, as doc/Makefile deliberately sets the environment variables to glob up as many Kconfig files as possible. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
2018-05-08 15:31:48 +08:00
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
choice
kconfig: Global whitespace/consistency cleanup Clean up space errors and use a consistent style throughout the Kconfig files. This makes reading the Kconfig files more distraction-free, helps with grepping, and encourages the same style getting copied around everywhere (meaning another pass hopefully won't be needed). Go for the most common style: - Indent properties with a single tab, including for choices. Properties on choices work exactly the same syntactically as properties on symbols, so not sure how the no-indentation thing happened. - Indent help texts with a tab followed by two spaces - Put a space between 'config' and the symbol name, not a tab. This also helps when grepping for definitions. - Do '# A comment' instead of '#A comment' I tweaked Kconfiglib a bit to find most of the stuff. Some help texts were reflowed to 79 columns with 'gq' in Vim as well, though not all, because I was afraid I'd accidentally mess up formatting. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 17:24:07 +08:00
prompt "Board Selection"
Kconfig: Use new preprocessor syntax for env. variables With the new Kconfig preprocessor (described in https://github.com/torvalds/linux/blob/master/Documentation/kbuild/ kconfig-macro-language.txt), the syntax for expanding environment variables is $(FOO) rather than $FOO. $(FOO) is a general preprocessor variable expansion, which falls back to environment variables if the variable isn't set (like in Make). It can also be used in prompts, 'comment's, etc. The old syntax will probably be supported forever in Kconfiglib for backwards compatibility, but might as well make it consistent now that people might start using the preprocessor more. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-09-05 19:10:19 +08:00
source "$(BOARD_DIR)/Kconfig.board"
kconfig: Global whitespace/consistency cleanup Clean up space errors and use a consistent style throughout the Kconfig files. This makes reading the Kconfig files more distraction-free, helps with grepping, and encourages the same style getting copied around everywhere (meaning another pass hopefully won't be needed). Go for the most common style: - Indent properties with a single tab, including for choices. Properties on choices work exactly the same syntactically as properties on symbols, so not sure how the no-indentation thing happened. - Indent help texts with a tab followed by two spaces - Put a space between 'config' and the symbol name, not a tab. This also helps when grepping for definitions. - Do '# A comment' instead of '#A comment' I tweaked Kconfiglib a bit to find most of the stuff. Some help texts were reflowed to 79 columns with 'gq' in Vim as well, though not all, because I was afraid I'd accidentally mess up formatting. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 17:24:07 +08:00
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
endchoice
boards: Kconfig: Enable use of shield conditional Kconfig files To make use of shields Kconfig.defconfig, parse these files and newly created Kconfig.shield files which will define the SHIELD_XXX Kconfig symbols that will be used for conditional configuration. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-11-22 17:37:01 +08:00
# Parse shields references
# Don't do it as a menuconfig, as shield selection is a CMake feature.
rsource "shields/*/Kconfig.shield"
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
boards: add a menu surrounding board Kconfig This adds a menu to enclose all board Kconfig. So the board configs do not appear on the top level out of context in menuconfig. This also reflects the SoC options where these are under menus for each architecture. Change-Id: I76ce2bf1acf7cbd2673ceb2eac71e96cdca2ff35 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 01:27:39 +08:00
menu "Board Options"
Kconfig: Switch to improved globbing statements A design flaw of 'gsource' is that there's no way to require at least one file to match the glob pattern. This could lead to silent errors. Switch to a new design, where a plain 'source' is globbing and requires at least one file to match. A separate 'osource' (optional source) statement is available for cases where it's okay for a pattern (or plain filename) to not match any files. 'orsource' combines 'osource' and 'rsource' (relative source). This commit search-replaces 'gsource' with 'source', but backwards compatibility with 'gsource' is still maintained by making it an alias for 'osource' (and by making 'grsource' an alias for 'orsource'). The three Kconfig files arch/{nios2,posix,xtensa}/Kconfig source arch/{nios2,posix,xtensa}/soc/*/Kconfig, which doesn't match any files. Use 'osource' for those. The soc/*/Kconfig files seem to be for additional SoC-specific symbols, only none exist yet on those ARCHes. Also use 'osource' for the source of $ENV_VAR_BOARD_DIR/Kconfig in boards/Kconfig, which doesn't exist for all boards. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 13:20:30 +08:00
# There might not be any board options, hence the optional source
Kconfig: Use new preprocessor syntax for env. variables With the new Kconfig preprocessor (described in https://github.com/torvalds/linux/blob/master/Documentation/kbuild/ kconfig-macro-language.txt), the syntax for expanding environment variables is $(FOO) rather than $FOO. $(FOO) is a general preprocessor variable expansion, which falls back to environment variables if the variable isn't set (like in Make). It can also be used in prompts, 'comment's, etc. The old syntax will probably be supported forever in Kconfiglib for backwards compatibility, but might as well make it consistent now that people might start using the preprocessor more. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-09-05 19:10:19 +08:00
osource "$(BOARD_DIR)/Kconfig"
boards: add a menu surrounding board Kconfig This adds a menu to enclose all board Kconfig. So the board configs do not appear on the top level out of context in menuconfig. This also reflects the SoC options where these are under menus for each architecture. Change-Id: I76ce2bf1acf7cbd2673ceb2eac71e96cdca2ff35 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 01:27:39 +08:00
endmenu