u-boot.git/common/Kconfig, branch master Unnamed repository; edit this file 'description' to name the repository. Add support for stack-protector 2021-04-20T11:31:12+00:00 Joel Peshkin joel.peshkin@broadcom.com 2021-04-11T09:21:58+00:00 4e9bce12432492aa7a7c2121d9fae1640606ace5 Add support for stack protector for UBOOT, SPL, and TPL as well as new pytest for stackprotector Signed-off-by: Joel Peshkin <joel.peshkin@broadcom.com> Adjust UEFI build flags. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
Add support for stack protector for UBOOT, SPL, and TPL
as well as new pytest for stackprotector

Signed-off-by: Joel Peshkin <joel.peshkin@broadcom.com>

Adjust UEFI build flags.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Convert CONFIG_MISC_INIT_F to Kconfig 2021-04-06T04:33:19+00:00 Simon Glass sjg@chromium.org 2021-03-26T03:17:30+00:00 48f45455bf1955ca1b2ba89bda256af2803a7126 This converts the following to Kconfig: CONFIG_MISC_INIT_F Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> 
This converts the following to Kconfig:
   CONFIG_MISC_INIT_F

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Stefan Roese <sr@denx.de>
common: SCP03 control (enable and provision of keys) 2021-03-13T18:14:52+00:00 Jorge Ramirez-Ortiz jorge@foundries.io 2021-02-14T15:27:23+00:00 166363f2ed9e72ed3e2bf09d9317d6a5fdafcbea This Trusted Application allows enabling SCP03 as well as provisioning the keys on TEE controlled secure element (ie, NXP SE050). All the information flowing on buses (ie I2C) between the processor and the secure element must be encrypted. Secure elements are pre-provisioned with a set of keys known to the user so that the secure channel protocol (encryption) can be enforced on the first boot. This situation is however unsafe since the keys are publically available. For example, in the case of the NXP SE050, these keys would be available in the OP-TEE source tree [2] and of course in the documentation corresponding to the part. To address that, users are required to rotate/provision those keys (ie, generate new keys and write them in the secure element's persistent memory). For information on SCP03, check the Global Platform HomePage and google for that term [1] [1] globalplatform.org [2] https://github.com/OP-TEE/optee_os/ check: core/drivers/crypto/se050/adaptors/utils/scp_config.c Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io> Reviewed-by: Simon Glass <sjg@chromium.org> 
This Trusted Application allows enabling SCP03 as well as provisioning
the keys on TEE controlled secure element (ie, NXP SE050).

All the information flowing on buses (ie I2C) between the processor
and the secure element must be encrypted. Secure elements are
pre-provisioned with a set of keys known to the user so that the
secure channel protocol (encryption) can be enforced on the first
boot. This situation is however unsafe since the keys are publically
available.

For example, in the case of the NXP SE050, these keys would be
available in the OP-TEE source tree [2] and of course in the
documentation corresponding to the part.

To address that, users are required to rotate/provision those keys
(ie, generate new keys and write them in the secure element's
persistent memory).

For information on SCP03, check the Global Platform HomePage and
google for that term [1]
[1] globalplatform.org
[2] https://github.com/OP-TEE/optee_os/
    check:
    core/drivers/crypto/se050/adaptors/utils/scp_config.c

Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
Reviewed-by: Simon Glass <sjg@chromium.org>
avb: AVB_VERIFY depends on MMC 2021-01-29T15:36:48+00:00 Heinrich Schuchardt xypron.glpk@gmx.de 2021-01-25T11:17:57+00:00 9c3808debad6cae03850a93af8f3d1a6677ca8c7 AVB Verified Boot uses functions related to MMC. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Igor Opaniuk <igor.opaniuk@foundries.io> 
AVB Verified Boot uses functions related to MMC.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Igor Opaniuk <igor.opaniuk@foundries.io>
bloblist: Support relocating to a larger space 2021-01-27T22:03:16+00:00 Simon Glass sjg@chromium.org 2021-01-14T03:29:43+00:00 9fe064646d2c9f3914cd5ceae51c34020aa77599 Typically in TPL/SPL the bloblist is quite small. But U-Boot proper may want to add a lot more to it, such as ACPI tables. Add a way to expand the bloblist by relocating it in U-Boot proper, along with the other relocation activities. Signed-off-by: Simon Glass <sjg@chromium.org> 
Typically in TPL/SPL the bloblist is quite small. But U-Boot proper may
want to add a lot more to it, such as ACPI tables.

Add a way to expand the bloblist by relocating it in U-Boot proper, along
with the other relocation activities.

Signed-off-by: Simon Glass <sjg@chromium.org>
common: Kconfig: Introduce CONFIG_CONSOLE_RECORD_INIT_F 2021-01-15T19:36:11+00:00 Ovidiu Panait ovidiu.panait@windriver.com 2020-11-28T08:43:03+00:00 4e81920ba8f426d381583c9b2e576230a0757db5 Currently, the following #ifdef construct is used to check whether to run console_record_init() during pre-relocation init: defined(CONFIG_CONSOLE_RECORD) && CONFIG_VAL(SYS_MALLOC_F_LEN) Introduce CONFIG_CONSOLE_RECORD_INIT_F Kconfig option to get rid of the complex ifdef check. Also, use IS_ENABLED() instead of #ifdef. Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Currently, the following #ifdef construct is used to check whether to run
console_record_init() during pre-relocation init:
 defined(CONFIG_CONSOLE_RECORD) && CONFIG_VAL(SYS_MALLOC_F_LEN)

Introduce CONFIG_CONSOLE_RECORD_INIT_F Kconfig option to get rid of the
complex ifdef check. Also, use IS_ENABLED() instead of #ifdef.

Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
common: update: add a generic interface for FIT image 2020-10-30T13:20:27+00:00 AKASHI Takahiro takahiro.akashi@linaro.org 2020-10-29T04:47:43+00:00 3149e524fc1e76ec1420cd17588c724d4232a904 The main purpose of this patch is to separate a generic interface for updating firmware using DFU drivers from "auto-update" via tftp. This function will also be used in implementing UEFI capsule update in a later commit. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Tom Rini <trini@konsulko.com> 
The main purpose of this patch is to separate a generic interface for
updating firmware using DFU drivers from "auto-update" via tftp.

This function will also be used in implementing UEFI capsule update
in a later commit.

Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
Kconfig: Move BOARD_TYPES under init options 2020-10-09T16:02:26+00:00 Simon Glass sjg@chromium.org 2020-09-11T02:21:26+00:00 a4c4ecf4c9b8768558a980d842c7db6fe35d570c This actually relates to something displayed on start-up, so move it into that menu. Signed-off-by: Simon Glass <sjg@chromium.org> 
This actually relates to something displayed on start-up, so move it into
that menu.

Signed-off-by: Simon Glass <sjg@chromium.org>
Kconfig: Move BOUNCE_BUFFER under driver options 2020-10-09T16:02:25+00:00 Simon Glass sjg@chromium.org 2020-09-11T02:21:25+00:00 d472d821f35a4b4e5a2d3302948a6f95d8cadfa5 This option does not belong at the top level. Move it under generic driver options. Signed-off-by: Simon Glass <sjg@chromium.org> 
This option does not belong at the top level. Move it under generic
driver options.

Signed-off-by: Simon Glass <sjg@chromium.org>
Kconfig: Move VERSION_VARIABLE under environment 2020-10-09T16:01:55+00:00 Simon Glass sjg@chromium.org 2020-09-11T02:21:24+00:00 bc438b6e9a25614dc11c3c3fa2c38f9133090740 This relates to the environment so should not be at the top level. Move it. Signed-off-by: Simon Glass <sjg@chromium.org> 
This relates to the environment so should not be at the top level. Move
it.

Signed-off-by: Simon Glass <sjg@chromium.org>