diff options
Diffstat (limited to 'common/Kconfig')
| -rw-r--r-- | common/Kconfig | 833 |
1 files changed, 381 insertions, 452 deletions
diff --git a/common/Kconfig b/common/Kconfig index d397d8bc4d..97a03217ea 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -1,8 +1,6 @@ -config DEFCONFIG_LIST - string - option defconfig_list - default ARCH_DEFCONFIG - default "arch/$(ARCH)/defconfig" +# SPDX-License-Identifier: GPL-2.0-only + +source "common/boards/Kconfig" config GREGORIAN_CALENDER bool @@ -16,7 +14,7 @@ config HAS_MODULES config HAS_CACHE bool help - This allows you do run "make ARCH=sandbox allyesconfig". + This allows you to run "make ARCH=sandbox allyesconfig". Drivers that depend on a cache implementation can depend on this config, so that you don't get a compilation error. @@ -24,11 +22,16 @@ config HAS_CACHE config HAS_DMA bool help - This allows you do run "make ARCH=sandbox allyesconfig". + This allows you to run "make ARCH=sandbox allyesconfig". Drivers that depend on a DMA implementation can depend on this config, so that you don't get a compilation error. +config ARCH_HAS_SJLJ + bool + help + Architecture has support implemented for setjmp()/longjmp()/initjmp() + config GENERIC_GPIO bool @@ -38,10 +41,6 @@ config BLOCK config BLOCK_WRITE bool -config ELF - bool - depends on MIPS - config FILETYPE bool @@ -69,31 +68,17 @@ config LOGBUF config STDDEV bool -config BAREBOX_UPDATE - bool - config MENUTREE bool select GLOB select GLOB_SORT -config EFI_GUID - bool - help - With this option a table of EFI guids is compiled in. - -config EFI_DEVICEPATH - bool - -config FILE_LIST - bool - config ARCH_DMA_ADDR_T_64BIT bool config BAREBOX_UPDATE_IMX_NAND_FCB bool - depends on ARCH_IMX6 || ARCH_IMX28 + depends on ARCH_IMX7 || ARCH_IMX6 || ARCH_IMX28 depends on BAREBOX_UPDATE depends on MTD_WRITE depends on NAND_MXS @@ -111,10 +96,13 @@ config USBGADGET_START bool depends on CMD_USBGADGET || USB_GADGET_AUTOSTART select ENVIRONMENT_VARIABLES - select FILE_LIST default y config BOOT + select GLOB + bool + +config FASTBOOT_BASE bool menu "General Settings" @@ -148,9 +136,6 @@ config LOCALVERSION_AUTO which is done within the script "scripts/setlocalversion".) -config BOARDINFO - string - config BANNER bool "display banner" default y @@ -159,6 +144,9 @@ config MEMINFO bool "display memory info" default y +config MEMTEST + bool + config ENVIRONMENT_VARIABLES bool "environment variables support" @@ -174,19 +162,19 @@ config GLOBALVAR config NVVAR bool "Non volatile global environment variables support" - default y if !SHELL_NONE + default y if !SHELL_NONE && ENV_HANDLING depends on GLOBALVAR - depends on ENV_HANDLING select FNMATCH help Non volatile environment variables begin with "nv.". They behave like - global variables above, but their values are saved in the environment - storage with 'saveenv' and thus are persistent over restarts. nv variables - are coupled with global variables of the same name. Setting "nv.foo" results - in "global.foo" changed also (but not the other way round: setting "global.foo" - leaves "nv.foo" untouched). The idea is that nv variables can store defaults - while global variables can be changed during runtime without changing the - default. + global variables above, but when CONFIG_ENV_HANDLING is enabled, they + can be stored in the environment storage with 'saveenv' and thus + persisted over restarts. nv variables are coupled with global + variables of the same name. Setting "nv.foo" results in "global.foo" + changed also (but not the other way round: setting "global.foo" leaves + "nv.foo" untouched). The idea is that nv variables can store defaults + while global variables can be changed during runtime without changing + the default. menu "memory layout" @@ -200,14 +188,8 @@ config MMU to enable the data cache which depends on the MMU. See Documentation/mmu.txt for further information. -config MMU_EARLY - bool "Enable MMU early" - depends on ARM - depends on MMU - default y - help - This enables the MMU during early startup. This speeds up things during startup - of barebox, but may lead to harder to debug code. If unsure say yes here. +config MMUINFO + bool config HAVE_CONFIGURABLE_TEXT_BASE bool @@ -216,9 +198,13 @@ config TEXT_BASE depends on HAVE_CONFIGURABLE_TEXT_BASE prompt "TEXT_BASE" hex + range 0 0xffffffff default ARCH_TEXT_BASE help - The Address barebox gets linked at. + The 32-bit address barebox gets linked at. This is forced + to zero for relocatable barebox and fixed up at runtime, + so barebox is executable on arbitrary addresses (given + sufficient alignment). config BAREBOX_MAX_IMAGE_SIZE prompt "Maximum size of barebox" @@ -291,6 +277,11 @@ config MALLOC_SIZE hex default 0x400000 prompt "malloc area size" + +config MALLOC_ALIGNMENT + hex + default 8 + endmenu config BROKEN @@ -317,18 +308,33 @@ config MALLOC_DUMMY memory is never freed. This is suitable for well tested noninteractive environments only. +config MALLOC_LIBC + bool "libc malloc" + depends on SANDBOX + help + select this option to use the libc malloc implementation in the sandbox. + This is benefecial for testing with external memory integrity tools. + endchoice config MODULES depends on HAS_MODULES depends on EXPERIMENTAL bool "module support" + modules help This option enables support for loadable modules via insmod. Module support is quite experimental at the moment. There is no convenient way to compile modules and the list of exported symbols to actually make use of modules is short to nonexistent +config HAVE_MOD_ARCH_SPECIFIC + bool + help + The arch uses struct mod_arch_specific to store data. Many arches + just need a simple module loader without arch specific data - those + should not enable this. + config KALLSYMS depends on HAS_KALLSYMS bool "kallsyms" @@ -337,7 +343,7 @@ config KALLSYMS This is useful to print a nice backtrace when an exception occurs. config RELOCATABLE - depends on PPC || ARM + depends on PPC || ARM || RISCV bool "generate relocatable barebox binary" help A non relocatable barebox binary will run at it's compiled in @@ -347,16 +353,40 @@ config RELOCATABLE allowing it to relocate to the end of the available RAM. This way you have the whole memory in a single piece. -config PANIC_HANG - bool "hang the system in case of a fatal error" - help - This option enables stop of the system in case of a - fatal error, so that you have to reset it manually. - This is probably NOT a good idea for an embedded - system where you want the system to reboot - automatically as fast as possible, but it may be - useful during development since you can try to debug - the conditions that lead to the situation. +choice + prompt "Configure action on fatal error" + default PANIC_RESET + + config PANIC_POWEROFF + bool "power off the system" + help + This option shuts down the system in case of a + fatal error, so that you have to power it on manually. + This is probably NOT a good idea for an embedded + system where you want the system to reboot + automatically as fast as possible, but it may be + useful in emulation, because the system returns + to parent shell immediately. + + config PANIC_HANG + bool "hang the system" + help + This option enables stop of the system in case of a + fatal error, so that you have to reset it manually. + This is probably NOT a good idea for an embedded + system where you want the system to reboot + automatically as fast as possible, but it may be + useful during development since you can try to debug + the conditions that lead to the situation. + + config PANIC_RESET + bool "reset the system" + help + This option enables reset of the system in case of a + fatal error, so you don't have to reset it manually. + This is the recommended configuration in production. + +endchoice config PROMPT string @@ -391,6 +421,7 @@ choice select PARAMETER select BINFMT select STDDEV + select GLOB help Enable hush support. This is the most advanced shell available for barebox. @@ -401,6 +432,8 @@ choice select COMMAND_SUPPORT select PARAMETER select STDDEV + select CMD_SETENV + select GLOB help simple shell. No if/then, no return values from commands, no loops @@ -515,15 +548,6 @@ endchoice endif -config DYNAMIC_CRC_TABLE - bool - depends on CRC32 - prompt "Generate the crc32 table dynamically" - default y - help - Saying yes to this option saves around 800 bytes of binary size. - If unsure say yes. - config ERRNO_MESSAGES bool prompt "print error values as text" @@ -532,16 +556,15 @@ config ERRNO_MESSAGES config TIMESTAMP bool default y + depends on UIMAGE select GREGORIAN_CALENDER - prompt "print timestamp information from images" + prompt "print timestamp information from uImages" help When CONFIG_TIMESTAMP is selected, the timestamp - (date and time) of an image is printed by image - commands like bootm or iminfo. This option is - automatically enabled when you select CFG_CMD_DATE . + (date and time) of an uImage is printed by image + commands like bootm or uimage. menuconfig BOOTM - select UIMAGE default y if COMMAND_SUPPORT bool "bootm support" @@ -585,10 +608,19 @@ config BOOTM_OFTREE -o DTS specify device tree +config BOOTM_UIMAGE + def_bool y + prompt "support the legacy uImage format" + select UIMAGE + depends on BOOTM + help + Support using uImages. This format has been superseded + by FIT images and is not as frequently used nowadays. + config BOOTM_OFTREE_UIMAGE bool prompt "support passing device tree (oftree) uImages" - depends on BOOTM_OFTREE + depends on BOOTM_OFTREE && BOOTM_UIMAGE help Support using oftree uImages. Without this only raw oftree blobs can be used. @@ -600,13 +632,27 @@ config BOOTM_AIMAGE help Support using Android Images. +config PE + bool "PE/COFF Support" if COMPILE_TEST + +config ELF + bool "ELF Support" if COMPILE_TEST + +config BOOTM_ELF + bool + depends on BOOTM + select ELF + prompt "elf loading support" + help + Add support to load elf file with bootm. + config BOOTM_FITIMAGE bool prompt "FIT image support" select FITIMAGE depends on BOOTM && ARM help - Support using Flattened Image Tree (FIT) Images. FIT is an image + Support using Flattened Image Tree (FIT) images. FIT is an image format introduced by U-Boot. A FIT image contains one or multiple kernels, device trees and initrds. The FIT image itself is a flattened device tree binary. Have a look at the u-boot source tree @@ -625,6 +671,22 @@ config BOOTM_FITIMAGE_SIGNATURE Additionally the barebox device tree needs a /signature node with the public key with which the image has been signed. +config BOOTM_FITIMAGE_PUBKEY_ENV + bool "Specify path to public key in environment" + depends on BOOTM_FITIMAGE_SIGNATURE + help + If this option is enabled the path to the device tree snippet + containing the public key for verifying FIT images signature is taken + from make's build-time environment, which can allow for better + integration with some build systems. + + The environment variable has the same name as the corresponding + Kconfig variable: + + CONFIG_BOOTM_FITIMAGE_PUBKEY + +if BOOTM_FITIMAGE_SIGNATURE && !BOOTM_FITIMAGE_PUBKEY_ENV + config BOOTM_FITIMAGE_PUBKEY string "Path to dtsi containing pubkey" default "../fit/pubkey.dtsi" @@ -634,6 +696,12 @@ config BOOTM_FITIMAGE_PUBKEY snippet can then be included in a device tree with "#include CONFIG_BOOTM_FITIMAGE_PUBKEY". + This snippet is usually generated by decompiling a device tree produced + by mkimage. An alternative is CONFIG_CRYPTO_RSA_KEY, which takes a PEM + file or a PKCS#11 URI. + +endif + config BOOTM_FORCE_SIGNED_IMAGES bool prompt "Force booting of signed images" @@ -643,27 +711,6 @@ config BOOTM_FORCE_SIGNED_IMAGES are refused to boot. Effectively this means only FIT images can be booted since they are the only supported image type that support signing. -config BOOTM_OPTEE - bool - prompt "support booting OP-TEE" - depends on BOOTM && ARM - help - OP-TEE is a trusted execution environment (TEE). With this option - enabled barebox supports starting optee_os as part of the bootm command. - Instead of the kernel bootm starts the optee_os binary which then starts - the kernel in nonsecure mode. Pass the optee_os binary with the -t option - or in the global.bootm.tee variable. - -config BOOTM_OPTEE_SIZE - hex - default 0x02000000 - prompt "OP-TEE Memory Size" - depends on BOOTM_OPTEE - help - Size to reserve in main memory for OP-TEE. - Can be smaller than the actual size used by OP-TEE, this is used to prevent - barebox from allocating memory in this area. - config BLSPEC depends on FLEXIBLE_BOOTARGS depends on !SHELL_NONE @@ -673,8 +720,8 @@ config BLSPEC bool prompt "Support bootloader spec" help - Enable this to let barebox support the Freedesktop bootloader spec, - see: http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ + Enable this to let barebox support the UAPI bootloader spec, + see: https://uapi-group.org/specifications/specs/boot_loader_specification/ The bootloader spec is a standard interface between the bootloader and the kernel. It allows the bootloader to discover boot options on a device and it allows the Operating System to install / update @@ -692,22 +739,50 @@ config FLEXIBLE_BOOTARGS to replace parts of the bootargs string without reconstructing it completely. +config MMCBLKDEV_ROOTARG + bool + prompt "Support 'root=mmcblkXpN' cmdline appending" + depends on FLEXIBLE_BOOTARGS + depends on MCI + depends on OFTREE + help + Enable this option to append 'root=mmcblkXpN' to the cmdline instead + of 'root=PARTUUID=XYZ'. Don't enable this option if your used linux + kernel doesn't contain commit [1]. The first linux kernel release + containing that commit is v5.10-rc1. + + The appending only happens if barebox' 'linux.bootargs.bootm.appendroot' + variable is set or the used blspec entry contains 'linux-appendroot'. + + Note: It is crucial that the kernel device tree and the barebox device + tree use the same mmc aliases. + + [1] fa2d0aa96941 ("mmc: core: Allow setting slot index via device tree + alias") + +config BAREBOX_UPDATE + bool "In-system barebox update infrastructure" + +config SYSTEM_PARTITIONS + bool "Generic system partitions support" + depends on GLOBALVAR + help + System partitions are a generic way for boards to specify the + partitions that should be exported for flashing. + Board drivers that set this directly will select this option + automatically. + Say y here if this should be configurable over the + global.system.partitions device parameter as well. + config IMD + select CRC32 bool "barebox metadata support" -config IMD_TARGET - bool "build bareboximd target tool" +config IMD_ENDIANNESS + bool "add endianness record to metadata" depends on IMD - depends on !SANDBOX - -config KERNEL_INSTALL_TARGET - bool - depends on !SANDBOX - prompt "Build kernel-install utility for the target" - help - Enable this to compile the kernel-install script using the cross - compiler. The utility for the target will be under - scripts/kernel-install-target + depends on SYS_SUPPORTS_LITTLE_ENDIAN && SYS_SUPPORTS_BIG_ENDIAN + default y choice prompt "console support" @@ -774,6 +849,27 @@ config CONSOLE_ALLOW_COLOR compile time default for colored console output. After boot it can be controlled using global.allow_color. +config CONSOLE_FLUSH_LINE_BREAK + bool "Flush consoles on new line" if COMPILE_TEST + help + Many serial drivers configure and use hardware FIFOs as not to + delay the boot. When debuging some king of bugs, such as clock + issues that hang the SoC, this can falsify debugging output, + because the UART doesn't output a submitted message fully, before + the SoC hangs. This option will flush serial FIFOs when processing + the new line feed characters. + +config CONSOLE_DISABLE_INPUT + prompt "Disable input on all consoles by default (non-interactive)" + def_bool CONSOLE_NONE + help + If enabled, all consoles are initially configured to not accept any input, + making the consoles effectively non-interactive. + The active device parameter can be used to override this on a per-console + basis. + CAUTION: this will also disable input devices by default, since they are + registered as consoles. + config PBL_CONSOLE depends on PBL_IMAGE depends on !CONSOLE_NONE @@ -791,6 +887,9 @@ config PARTITION bool prompt "Enable Partitions" +config PARTITION_MANIPULATION + bool + source "common/partitions/Kconfig" config ENV_HANDLING @@ -804,13 +903,14 @@ config ENV_HANDLING startup) will bring them back. If unsure, say yes. config DEFAULT_ENVIRONMENT + select CRC32 bool - default y - depends on ENV_HANDLING + default y if ENV_HANDLING prompt "Compile in default environment" help Enabling this option will give you a default environment when - the environment found in the environment sector is invalid + the environment found in the environment sector is invalid or when + CONFIG_ENV_HANDLING is not enabled. choice prompt "default compression for in-barebox binaries" @@ -821,29 +921,30 @@ choice default DEFAULT_COMPRESSION_LZ4 if LZ4_DECOMPRESS default DEFAULT_COMPRESSION_BZIP2 if BZLIB help - Select the default compression for in-barebox binary files. Files - compiled into barebox like for example the default environment will - be compressed with this compression type. + For barebox builds without a prebootloader, select here the default + compression for in-barebox binary files. barebox itself can't be + compressed without a prebootloader, but for example the default + environment will be compressed with this compression type. config DEFAULT_COMPRESSION_GZIP bool "gzip" - depends on ZLIB + depends on !PBL_IMAGE && ZLIB config DEFAULT_COMPRESSION_BZIP2 bool "bzip2" - depends on BZLIB + depends on !PBL_IMAGE && BZLIB config DEFAULT_COMPRESSION_LZO bool "lzo" - depends on LZO_DECOMPRESS + depends on !PBL_IMAGE && LZO_DECOMPRESS config DEFAULT_COMPRESSION_LZ4 bool "lz4" - depends on LZ4_DECOMPRESS + depends on !PBL_IMAGE && LZ4_DECOMPRESS config DEFAULT_COMPRESSION_XZ bool "xz" - depends on XZ_DECOMPRESS + depends on !PBL_IMAGE && XZ_DECOMPRESS config DEFAULT_COMPRESSION_NONE bool "no compression" @@ -873,6 +974,13 @@ config DEFAULT_ENVIRONMENT_GENERIC_NEW select NET_CMD_IFUP if NET select CMD_IP_ROUTE_GET if NET select CMD_HOST if NET + help + With this option barebox will use the files found under + defaultenv/defaultenv-2-base/ in the source tree as a template for + the defaultenv. The directories specified in DEFAULT_ENVIRONMENT_PATH + will be added to the default environment. If a file is present in + both locations, the file from DEFAULT_ENVIRONMENT_PATH will overwrite + that from the template. config DEFAULT_ENVIRONMENT_GENERIC bool "Generic environment template (old version)" @@ -886,9 +994,12 @@ config DEFAULT_ENVIRONMENT_GENERIC select CMD_CRC_CMP select CMD_GLOBAL help - With this option barebox will use the generic default - environment found under defaultenv/ in the src tree. - The Directory given with DEFAULT_ENVIRONMENT_PATH + Note: this option is not recommended for new boards; use + DEFAULT_ENVIRONMENT_GENERIC_NEW instead. + + With this option barebox will use the old generic default environment + found under defaultenv/defaultenv-1/ in the source tree. + The directory given with DEFAULT_ENVIRONMENT_PATH will be added to the default environment. This should at least contain a /env/config file. This will be able to overwrite the files from defaultenv. @@ -898,40 +1009,56 @@ config DEFAULT_ENVIRONMENT_GENERIC_NEW_MENU depends on DEFAULT_ENVIRONMENT_GENERIC_NEW depends on CMD_MENUTREE default y + help + Extend the defaultenv template with a menu that is displayed at boot. + The menu files are taken from defaultenv/defaultenv-2-menu/. config DEFAULT_ENVIRONMENT_GENERIC_NEW_DFU bool depends on DEFAULT_ENVIRONMENT_GENERIC_NEW depends on USB_GADGET_DFU default y + help + Extend the defaultenv template with the 'dfu' boot entry, which + allows uploading the kernel and oftree over USB via the dfu protocol. + +config DEFAULT_ENVIRONMENT_GENERIC_NEW_REBOOT_MODE + bool "Generic reboot-mode handlers in the environment" + depends on DEFAULT_ENVIRONMENT_GENERIC_NEW + depends on REBOOT_MODE + +config DEFAULT_ENVIRONMENT_GENERIC_NEW_IKCONFIG + bool "Ship .config as /env/data/config" + depends on DEFAULT_ENVIRONMENT_GENERIC_NEW + help + This option embeds the used barebox Kconfig .config file into the + environment as /env/data/config. This will increase barebox' image + size. If unsure, say n here. config DEFAULT_ENVIRONMENT_PATH string depends on DEFAULT_ENVIRONMENT prompt "Default environment path" help - Space separated list of paths the default environment will be taken from. - Relative paths will be relative to the barebox Toplevel dir, but absolute - paths are fine aswell. - -config BAREBOXENV_TARGET - bool - depends on !SANDBOX - prompt "build bareboxenv tool for target" - help - 'bareboxenv' is a tool to access the barebox environment from a running Linux - system. Say yes here to build it for the target. + Space separated list of paths from which the default environment will + be taken. Relative paths will be relative to the barebox top-level + directory, but absolute paths are fine as well. -config BAREBOXCRC32_TARGET +config HAS_SCHED bool - prompt "build bareboxcrc32 tool for target" - depends on !SANDBOX - help - 'bareboxcrc32' is a userspacetool to generate the crc32 checksums the same way - barebox does. Say yes here to build it for the target. config POLLER bool "generic polling infrastructure" + select HAS_SCHED + +config BTHREAD + bool "barebox co-operative (green) thread infrastructure" + select HAS_SCHED + depends on ARCH_HAS_SJLJ + help + barebox threads are lightweight cooperative (green) threads that are + scheduled within delay loops and the console idle to asynchronously + execute actions, like checking for link up or feeding a watchdog. config STATE bool "generic state infrastructure" @@ -939,6 +1066,13 @@ config STATE select ENVIRONMENT_VARIABLES select OFTREE select PARAMETER + imply STATE_DRV + imply CMD_STATE + help + barebox state is a generic framework for atomic power fail-safe + variable storage and retrieval. It can be used to safely maintain + data over reboots and to exchange information with Linux, e.g. + for redundant boot with bootchooser. config STATE_CRYPTO bool "HMAC based authentication support" @@ -947,7 +1081,7 @@ config STATE_CRYPTO select DIGEST select DIGEST_HMAC_GENERIC help - This options enables HMAC based authentication support for + This option enables HMAC based authentication support for the state's header and data. This means the state framework can verify both the data integrity and the authentication of the state's header and data. @@ -978,359 +1112,154 @@ config RESET_SOURCE bool "detect Reset cause" depends on GLOBALVAR help - Provide a global variable at runtine which reflects the possible cause + Provide a global variable at runtime which reflects the possible cause of the reset and why the bootloader is currently running. It can be useful for any kind of system recovery or repair. config MACHINE_ID - bool "pass machine-id to kernel" + bool "compute unique machine-id" depends on FLEXIBLE_BOOTARGS - depends on SHA1 + depends on HAVE_DIGEST_SHA1 help - Sets the linux.bootargs.machine_id global variable with a value of - systemd.machine_id=UID. The UID is a persistent device-specific - id. It is a hash over device-specific information provided by various - sources. + Compute a persistent machine-specific id and store it to $global.machine_id. + The id is a hash of device-specific information added via + machine_id_set_hashable(). If multiple sources are available, the + information provided by the last call prior to the late initcall + set_machine_id() is used to generate the machine id from. Thus when + updating barebox the machine id might change. - Note: if multiple sources provide hashable device-specific information - (via machine_id_set_hashable()) the information provided by the last call - prior to the late initcall set_machine_id() is used to generate the - machine id from. Thus when updating barebox the machine id might change. + global.bootm.provide_machine_id may be used to automatically set + the linux.bootargs.machine_id global variable with a value of + systemd.machine_id=${global.machine_id} Note: if no hashable information is available no machine id will be passed to the kernel. -endmenu - -menu "Debugging" - -config COMPILE_LOGLEVEL - int "compile loglevel" - default 6 - help - This defines the maximum loglevel compiled into the binary. Less important - messages will be compiled away resulting in a smaller binary. - - 0 system is unusable (emerg) - 1 action must be taken immediately (alert) - 2 critical conditions (crit) - 3 error conditions (err) - 4 warning conditions (warn) - 5 normal but significant condition (notice) - 6 informational (info) - 7 debug-level messages (debug) - 8 verbose debug messages (vdebug) - -config DEFAULT_LOGLEVEL - int "default loglevel" - default 7 - help - This defines the default runtime loglevel. It can be changed using the - global.loglevel variable. Available logelevels are: - - 0 system is unusable (emerg) - 1 action must be taken immediately (alert) - 2 critical conditions (crit) - 3 error conditions (err) - 4 warning conditions (warn) - 5 normal but significant condition (notice) - 6 informational (info) - 7 debug-level messages (debug) - 8 verbose debug messages (vdebug) - -config DEBUG_LL - bool - depends on HAS_DEBUG_LL - prompt "Low level debug messages (read help)" - help - Enable this to get low level debug messages during barebox - initialization. This is helpful if you are debugging code that - executes before the console is initialized. - - This requires SoC specific support. Most SoCs require the - debug UART to be initialized by a debugger or first stage - bootloader. - - Note that selecting this option will limit barebox to a single - UART definition, as specified below under "low-level debugging - port". Attempting to boot the resulting image on a different - platform *will not work*, so this option should not be enabled - for builds that are intended to be portable. - -choice - prompt "Kernel low-level debugging port" - depends on DEBUG_LL - -config DEBUG_IMX1_UART - bool "i.MX1 Debug UART" - depends on ARCH_IMX1 - help - Say Y here if you want kernel low-level debugging support - on i.MX1. - -config DEBUG_IMX21_UART - bool "i.MX21 Debug UART" - depends on ARCH_IMX21 - help - Say Y here if you want kernel low-level debugging support - on i.MX21. - -config DEBUG_IMX25_UART - bool "i.MX25 Debug UART" - depends on ARCH_IMX25 - help - Say Y here if you want kernel low-level debugging support - on i.MX25. - -config DEBUG_IMX27_UART - bool "i.MX27 Debug UART" - depends on ARCH_IMX27 +config SYSTEMD_OF_WATCHDOG + bool "inform devicetree-enabled kernel of used watchdog" + depends on WATCHDOG && OFTREE && FLEXIBLE_BOOTARGS help - Say Y here if you want kernel low-level debugging support - on i.MX27. + Sets the linux.bootargs.dyn.watchdog global variable with a value of + systemd.watchdog-device=/dev/WDOG if barebox succeeded in enabling + the watchdog WDOG prior to boot. WDOG is the alias of the watchdog + in the kernel device tree. If the kernel is booted without a device + tree or with one that lacks aliases, nothing is added. -config DEBUG_IMX31_UART - bool "i.MX31 Debug UART" - depends on ARCH_IMX31 +config EXTERNAL_DTS_FRAGMENTS + string "external dts file fragments" + depends on OFTREE help - Say Y here if you want kernel low-level debugging support - on i.MX31. + List of dts fragment files that will be appended to Barebox's device + tree(s) source when building the dtb file(s). If multiple files are + listed, they will be appended in order. Relative filenames will use + the dtc include search path. -config DEBUG_IMX35_UART - bool "i.MX35 Debug UART" - depends on ARCH_IMX35 - help - Say Y here if you want kernel low-level debugging support - on i.MX35. - -config DEBUG_IMX50_UART - bool "i.MX50 Debug UART" - depends on ARCH_IMX50 - help - Say Y here if you want kernel low-level debugging support - on i.MX50. - -config DEBUG_IMX51_UART - bool "i.MX51 Debug UART" - depends on ARCH_IMX51 - help - Say Y here if you want kernel low-level debugging support - on i.MX51. - -config DEBUG_IMX53_UART - bool "i.MX53 Debug UART" - depends on ARCH_IMX53 - help - Say Y here if you want kernel low-level debugging support - on i.MX53. - -config DEBUG_IMX6Q_UART - bool "i.MX6Q Debug UART" - depends on ARCH_IMX6 - help - Say Y here if you want kernel low-level debugging support - on i.MX6Q. + A preprocessor macro based on the name of the main dts will be + defined, which allows the dts fragments to be based on which image of + a multi image build they are being used in. Given the dts filename + used for a board is "foo-board.dts" the external dts usage can be + limited to that board with -config DEBUG_IMX7D_UART - bool "i.MX7D Debug UART" - depends on ARCH_IMX7 - help - Say Y here if you want barebox low-level debugging support - on i.MX7D. - -config DEBUG_IMX8MQ_UART - bool "i.MX8MQ Debug UART" - depends on ARCH_IMX8MQ - help - Say Y here if you want barebox low-level debugging support - on i.MX8MQ. + #ifdef foo_board_dts + ... + #endif -config DEBUG_VF610_UART - bool "VF610 Debug UART" - depends on ARCH_VF610 - help - Say Y here if you want kernel low-level debugging support - on VF610. + It is not intended that this is put into Barebox' defconfig files. + Instead, it's an external build system's job, like Yocto or buildroot, + to add dts fragments from outside the Barebox source tree into the + Barebox build. -config DEBUG_OMAP3_UART - bool "OMAP3 Debug UART" - depends on ARCH_OMAP3 - help - Say Y here if you want kernel low-level debugging support - on OMAP3. +menu "OP-TEE loading" -config DEBUG_OMAP4_UART - bool "OMAP4 Debug UART" - depends on ARCH_OMAP4 +config HAVE_OPTEE + bool help - Say Y here if you want kernel low-level debugging support - on OMAP4. + This symbol is selected by configuration where barebox either + starts OP-TEE or runs while OP-TEE is running. Actual + bidirectional communication with OP-TEE is enabled via + CONFIG_OPTEE. -config DEBUG_AM33XX_UART - bool "AM33XX Debug UART" - depends on ARCH_AM33XX +config OPTEE_SIZE + hex + default 0x02000000 + prompt "OP-TEE Memory Size" + depends on HAVE_OPTEE help - Say Y here if you want kernel low-level debugging support - on AM33XX. + Size to reserve in main memory for OP-TEE. + Can be smaller than the actual size used by OP-TEE, this is used to prevent + barebox from allocating memory in this area. -config DEBUG_ROCKCHIP_UART - bool "RK3xxx Debug UART" - depends on ARCH_ROCKCHIP +config OPTEE_SHM_SIZE + hex + default 0x400000 + prompt "OP-TEE Shared Memory Size" + depends on HAVE_OPTEE help - Say Y here if you want kernel low-level debugging support - on RK3XXX. + Size to reserve in main memory for OP-TEE shared memory communication. + Can be used for fixing up the OP-TEE OF node. -config DEBUG_SOCFPGA_UART0 - bool "Use SOCFPGA UART0 for low-level debug" - depends on ARCH_SOCFPGA +config BOOTM_OPTEE + bool + prompt "support booting OP-TEE" + depends on BOOTM && ARM && 32BIT + select HAVE_OPTEE help - Say Y here if you want kernel low-level debugging support - on SOCFPGA(Cyclone 5 and Arria 5) based platforms. + OP-TEE is a trusted execution environment (TEE). With this option + enabled barebox supports starting optee_os as part of the bootm command. + Instead of the kernel bootm starts the optee_os binary which then starts + the kernel in nonsecure mode. Pass the optee_os binary with the -t option + or in the global.bootm.tee variable. -config DEBUG_SOCFPGA_UART1 - bool "Use SOCFPGA UART1 for low-level debug" - depends on ARCH_SOCFPGA +config PBL_OPTEE + bool "Enable OP-TEE early start" + depends on ARM + depends on !THUMB2_BAREBOX + select HAVE_OPTEE help - Say Y here if you want kernel low-level debugging support - on SOCFPGA(Arria 10) based platforms. + Allows starting OP-TEE during lowlevel initialization of the PBL. + Requires explicit support in the board's lowlevel file. -config DEBUG_RPI1_UART - bool "RaspberryPi 1 PL011 UART" - depends on ARCH_BCM283X - help - Say Y here if you want low-level debugging support on - RaspberryPi 1 boards. +endmenu -config DEBUG_AT91_UART - bool "AT91 Debug UART" - depends on ARCH_AT91 - help - Say Y here if you want barebox low-level debugging support - on AT91 based platforms. +if FASTBOOT_BASE -config DEBUG_RPI2_3_UART - bool "RaspberryPi 2/3 PL011 UART" - depends on ARCH_BCM283X - help - Say Y here if you want low-level debugging support on - RaspberryPi 2 and 3 boards. +menu "Android Fastboot" -config DEBUG_RPI3_MINI_UART - bool "RaspberryPi 3 mini UART" - depends on ARCH_BCM283X +config FASTBOOT_SPARSE + bool + select IMAGE_SPARSE + prompt "Enable Fastboot sparse image support" help - Say Y here if you want low-level debugging support on - RaspberryPi 3 board mini UART. -endchoice + Sparse images are a way for the fastboot protocol to write + images that are bigger than the available memory. If unsure, + say yes here. -config DEBUG_IMX_UART_PORT - int "i.MX Debug UART Port Selection" if DEBUG_IMX1_UART || \ - DEBUG_IMX21_UART || \ - DEBUG_IMX25_UART || \ - DEBUG_IMX27_UART || \ - DEBUG_IMX31_UART || \ - DEBUG_IMX35_UART || \ - DEBUG_IMX51_UART || \ - DEBUG_IMX53_UART || \ - DEBUG_IMX6Q_UART || \ - DEBUG_IMX6SL_UART || \ - DEBUG_IMX7D_UART || \ - DEBUG_IMX8MQ_UART || \ - DEBUG_VF610_UART - default 1 - depends on ARCH_IMX - help - Choose UART port on which kernel low-level debug messages - should be output. - -config DEBUG_OMAP_UART_PORT - int "OMAP Debug UART Port Selection" if DEBUG_OMAP3_UART || \ - DEBUG_OMAP4_UART || \ - DEBUG_AM33XX_UART - default 1 - depends on ARCH_OMAP - help - Choose UART port on which kernel low-level debug messages - should be output. Possible values are: - OMAP3: 1 - 3 - OMAP4: 1 - 3 - AM33XX: 0 - 2 - -config DEBUG_ROCKCHIP_UART_PORT - int "RK3xxx UART debug port" if DEBUG_ROCKCHIP_UART - default 2 - depends on ARCH_ROCKCHIP - help - Choose UART port on which kernel low-level debug messages - should be output. - -config DEBUG_SOCFPGA_UART_PHYS_ADDR - hex "Physical base address of debug UART" if DEBUG_LL - default 0xffc02000 if DEBUG_SOCFPGA_UART0 - default 0xffc02100 if DEBUG_SOCFPGA_UART1 - depends on ARCH_SOCFPGA - -config DEBUG_SOCFPGA_UART_CLOCK - int "SoCFPGA UART debug clock" if DEBUG_LL - default 100000000 if ARCH_SOCFPGA_CYCLONE5 - default 50000000 if ARCH_SOCFPGA_ARRIA10 - depends on ARCH_SOCFPGA - help - Choose UART root clock. - - -config DEBUG_LAYERSCAPE_UART_PORT - int "Layerscape UART port selection" - depends on ARCH_LAYERSCAPE - default 1 - help - Select the UART port number used for early debugging here. Port - numbers start counting from 1. - -config DEBUG_AT91_UART_BASE - hex "AT91 Debug UART Port Selection" if DEBUG_AT91_UART - default 0xfffff200 if SOC_AT91RM9200 || SOC_AT91SAM9260 \ - || SOC_AT91SAM9261 || SOC_AT91SAM9X5 \ - || SOC_AT91SAM9N12 - default 0xffffee00 if SOC_AT91SAM9263 || SOC_AT91SAM9G45 || SOC_SAMA5D3 - default 0xfc069000 if SOC_SAMA5D4 - default 0xf8020000 if SOC_SAMA5D2 - default 0xfffff200 - depends on ARCH_AT91 - help - Specify UART port base address on which barebox low-level - debug messages should be output. - -config DEBUG_INITCALLS - bool "Trace initcalls" - help - If enabled this will print initcall traces. - - -config PBL_BREAK - bool "Execute software break on pbl start" - depends on ARM +config FASTBOOT_CMD_OEM + bool + prompt "Enable OEM commands" help - If this enabled, barebox will be compiled with BKPT instruction - on early pbl init. This option should be used only with JTAG debugger! + This option enables the fastboot "oem" group of commands. They allow to + executing arbitrary barebox commands and may be disabled in secure + environments. -source "lib/Kconfig.ubsan" +endmenu -config KASAN - bool "KASAN: runtime memory debugger" - depends on HAVE_ARCH_KASAN - help - Enables KASAN (KernelAddressSANitizer) - runtime memory debugger, - designed to find out-of-bounds accesses and use-after-free bugs. +endif endmenu -config HAS_DEBUG_LL - bool +source "common/Kconfig.debug" +source "common/boards/Kconfig" config DDR_SPD bool select CRC_ITU_T -config HAVE_ARCH_KASAN +config HAVE_ARCH_ASAN bool + +config ARCH_USE_SYM_ANNOTATIONS + bool + help + This is selected by architectures that exclusively use the new SYM_ + macros in their assembly code and not the deprecated ENTRY/PROC. |