September 2022 - U-Boot

[PATCH v2 1/1] lib: rsa: fix padding_pss_verify
by Heinrich Schuchardt 15 Sep '22

15 Sep '22

Check the that the hash length is shorter than the message length. This avoids: ./tools/../lib/rsa/rsa-verify.c:275:11: warning: ‘*db’ may be used uninitialized [-Wmaybe-uninitialized] 275 | db[0] &= 0xff >> leftmost_bits; Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt(a)canonical.com> --- v2: Use -EINVAL to indicate incorrect parameters. Add description of return value. --- lib/rsa/rsa-verify.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lib/rsa/rsa-verify.c b/lib/rsa/rsa-verify.c index 1d95cfbdee..f13cd23cf2 100644 --- a/lib/rsa/rsa-verify.c +++ b/lib/rsa/rsa-verify.c @@ -215,6 +215,8 @@ out: * @msg_len: Message length * @hash: Pointer to the expected hash * @hash_len: Length of the hash + * + * Return: 0 if padding is correct, non-zero otherwise */ int padding_pss_verify(struct image_sign_info *info, const uint8_t *msg, int msg_len, @@ -234,6 +236,9 @@ int padding_pss_verify(struct image_sign_info *info, uint8_t leftmost_mask; struct checksum_algo *checksum = info->checksum; + if (db_len <= 0) + return -EINVAL; + /* first, allocate everything */ db_mask = malloc(db_len); db = malloc(db_len); -- 2.37.2

3 2

[PATCHv5] drivers: tee: i2c: support the NXP SE05x probe errata
by Jorge Ramirez-Ortiz 15 Sep '22

15 Sep '22

Early instantiation of this I2C device would lock up when being probed. https://www.nxp.com/docs/en/errata/SE050_Erratasheet.pdf 3.2.2 In scenarios of detecting I2C ICs on the bus using an empty I2C frame containing only the address the SE050 will block the I2C bus. Tested on STM32MP1 Signed-off-by: Jorge Ramirez-Ortiz <jorge(a)foundries.io> Acked-by: Oleksandr Suvorov <oleksandr.suvorov(a)foundries.io> --- v5: address Kconfig issue with select (remove) v4: address build issue when feature not enabled v3,2,1: no changes (were part of a patchset) drivers/tee/optee/Kconfig | 13 ++++++++++++ drivers/tee/optee/i2c.c | 44 +++++++++++++++++++++++++++++++++++---- 2 files changed, 53 insertions(+), 4 deletions(-) diff --git a/drivers/tee/optee/Kconfig b/drivers/tee/optee/Kconfig index d03028070b..8b02b71be2 100644 --- a/drivers/tee/optee/Kconfig +++ b/drivers/tee/optee/Kconfig @@ -37,6 +37,19 @@ config OPTEE_TA_SCP03 help Enables support for controlling (enabling, provisioning) the Secure Channel Protocol 03 operation in the OP-TEE SCP03 TA. + +config TEE_I2C_NXP_SE05X_ERRATA + bool "Enable NXP SE05X Errata" + default n + help + This config prevents the I2C trampoline driver from probing + on every transfer. + +config TEE_I2C_NXP_SE05X_ERRATA_IN_BUS + int "I2C bus where to apply the NXP SE05X errata" + depends on TEE_I2C_NXP_SE05X_ERRATA + default 0 + endmenu endif diff --git a/drivers/tee/optee/i2c.c b/drivers/tee/optee/i2c.c index ef4e10f991..e1b2534909 100644 --- a/drivers/tee/optee/i2c.c +++ b/drivers/tee/optee/i2c.c @@ -3,13 +3,18 @@ * Copyright (c) 2020 Foundries.io Ltd */ +#define LOG_CATEGORY UCLASS_I2C + #include <common.h> #include <dm.h> #include <i2c.h> +#include <stdlib.h> #include <tee.h> #include "optee_msg.h" #include "optee_private.h" +#define NXP_SE05X_ADDR 0x48 + static int check_xfer_flags(struct udevice *chip, uint tee_flags) { uint flags; @@ -30,6 +35,30 @@ static int check_xfer_flags(struct udevice *chip, uint tee_flags) return 0; } +static struct udevice *get_chip_dev(int bnum, int addr) +{ + struct udevice *chip; + struct udevice *bus; + +#if defined(CONFIG_TEE_I2C_NXP_SE05X_ERRATA) + if (bnum == CONFIG_TEE_I2C_NXP_SE05X_ERRATA_IN_BUS && + addr == NXP_SE05X_ADDR) { + if (uclass_get_device_by_seq(UCLASS_I2C, bnum, &bus)) + return NULL; + + if (i2c_get_chip(bus, addr, 0, &chip)) + return NULL; + + return chip; + } +#endif + + if (i2c_get_chip_for_busnum(bnum, addr, 0, &chip)) + return NULL; + + return chip; +} + void optee_suppl_cmd_i2c_transfer(struct optee_msg_arg *arg) { const u8 attr[] = { @@ -38,7 +67,8 @@ void optee_suppl_cmd_i2c_transfer(struct optee_msg_arg *arg) OPTEE_MSG_ATTR_TYPE_RMEM_INOUT, OPTEE_MSG_ATTR_TYPE_VALUE_OUTPUT, }; - struct udevice *chip_dev; + struct udevice *chip_dev = NULL; + struct tee_shm *shm; u8 *buf; int ret; @@ -56,9 +86,9 @@ void optee_suppl_cmd_i2c_transfer(struct optee_msg_arg *arg) if (!buf) goto bad; - if (i2c_get_chip_for_busnum((int)arg->params[0].u.value.b, - (int)arg->params[0].u.value.c, - 0, &chip_dev)) + chip_dev = get_chip_dev((int)arg->params[0].u.value.b, + (int)arg->params[0].u.value.c); + if (!chip_dev) goto bad; if (check_xfer_flags(chip_dev, arg->params[1].u.value.a)) @@ -66,10 +96,16 @@ void optee_suppl_cmd_i2c_transfer(struct optee_msg_arg *arg) switch (arg->params[0].u.value.a) { case OPTEE_MSG_RPC_CMD_I2C_TRANSFER_RD: + log_debug("OPTEE_MSG_RPC_CMD_I2C_TRANSFER_RD %d\n", + (size_t)arg->params[2].u.rmem.size); + ret = dm_i2c_read(chip_dev, 0, buf, (size_t)arg->params[2].u.rmem.size); break; case OPTEE_MSG_RPC_CMD_I2C_TRANSFER_WR: + log_debug("OPTEE_MSG_RPC_CMD_I2C_TRANSFER_WR %d\n", + (size_t)arg->params[2].u.rmem.size); + ret = dm_i2c_write(chip_dev, 0, buf, (size_t)arg->params[2].u.rmem.size); break; -- 2.34.1

3 3

[U-Boot][bug report] clearfog: EMMC boot broken on clearfog pro
by Florian Kaiser 15 Sep '22

15 Sep '22

Hi, I am using a clearfog pro with emmc as router. while upgrading from openwrt 21.02.3 to 22.03.0 I discovered, that the provided u-boot binary gets rejected by the BootROM: -> BootROM - 1.73 -> Booting from MMC -> BootROM: Bad header at offset 00000000 -> BootROM: Bad header at offset 00200000 -> Switching BootPartitions. -> BootROM: Invalid HDR source addr While comparing the different u-boot-spl.kwb between openwrt 21.02.3 (u-boot 2021.01) and openwrt 22.03.0 (u-boot 2022.07) I saw that the image has changed from a gpimage to the kwbimage v1. After reading some code, my gut feeling told me, that maybe the BootROM does not like the HDR source addr because it does not expect it to be in sectors but in Bytes. After binary patching the the srcaddr (srcaddr = srcaddr * 512) in the kwbimage v1 header, I got the BootROM to execute the SPL again. -> Booting from MMC -> U-Boot SPL 2022.07-OpenWrt-r19685-512e76967f (Sep 03 2022 - 02:55:34 +0000) -> High speed PHY - Version: 2.0 -> EEPROM TLV detection failed: Using static config for Clearfog Pro. -> Detected Device ID 6828 -> board SerDes lanes topology details: -> | Lane # | Speed | Type | -> -------------------------------- -> | 0 | 3 | SATA0 | -> | 1 | 0 | SGMII1 | -> | 2 | 5 | PCIe1 | -> | 3 | 5 | USB3 HOST1 | -> | 4 | 5 | PCIe2 | -> | 5 | 0 | SGMII2 | -> -------------------------------- -> High speed PHY - Ended Successfully -> mv_ddr: 14.0.0 -> DDR3 Training Sequence - Switching XBAR Window to FastPath Window -> mv_ddr: completed successfully -> Trying to boot from MMC1 -> ERROR: Invalid kwbimage v1 -> ERROR: Invalid data checksum in kwbimage -> SPL: failed to boot from all boot devices -> ### ERROR ### Please RESET the board ### I think I do understand the problem here, but I am not quite sure whats the best way to move forward. Unfortunately I am not that familiar with the u-boot sourcecode... Could you give me some pointers, where to start for an integrate-able solution? Thanks!

1 0

Re: [PATCH v1] wdt: nuvoton: add expire function for generic reset
by Jim Liu 15 Sep '22

15 Sep '22

Hi Stefan Roese Thanks for your review. Here is my log from uboot master. And i add the debug log as below: ----------------------------------------------- U-Boot 2022.10-rc4-00038-ge3fce5e560-dirty (Sep 15 2022 - 09:58:25 +0800) CPU: NPCM750 A1 @ Model: Nuvoton npcm750 Development Board (Device Tree) DRAM: 464 MiB RNG: NPCM RNG module bind OK OTP: NPCM OTP module bind OK AES: NPCM AES module bind OK SHA: NPCM SHA module bind OK Core: 210 devices, 22 uclasses, devicetree: separate WDT: Started watchdog@801C without servicing (60s timeout) MMC: sdhci0@f0842000: 0 Loading Environment from SPIFlash... SF: Detected mx66l51235l with page size 256 Bytes, erase size 64 KiB, total 64 MiB OK In: serial@1000 Out: serial@1000 Err: serial@1000 Net: eth0: eth@f0802000, eth1: eth@f0825000 Hit any key to stop autoboot: 0 U-Boot>reset resetting ... jim[wdt_reboot_request] jim[npcm_wdt_expire_now] jim[npcm_wdt_reset] >================================================ > BootBlock by Nuvoton Technology Corp. Ver 10.10.17 >================================================ BB Basic Mar 24 2021 12:06:08 >CORSTC = 0x4fff9f9d >WD0RCR = 0x4fff9f9d >WD1RCR = 0x4fff9f9d >WD2RCR = 0x4fff9f9d >SWRSTC1 = 0x4fff9f9d >SWRSTC2 = 0x4fff9f9d >SWRSTC3 = 0x4fff9f9d ---------------------------------------------------- If you have any suggestions, please provide to me. I will follow to modify it. Best regards, Jim On Thu, Sep 15, 2022 at 10:23 AM JJLIU0(a)nuvoton.com <JJLIU0(a)nuvoton.com> wrote: > > > > -----Original Message----- > From: Stefan Roese <sr(a)denx.de> > Sent: Wednesday, September 14, 2022 2:27 PM > To: Jim Liu <jim.t90615(a)gmail.com>; CS20 JJLiu0 <JJLIU0(a)nuvoton.com>; CS20 YSChu <YSCHU(a)nuvoton.com>; CS20 KWLiu <KWLIU(a)nuvoton.com> > Cc: u-boot(a)lists.denx.de > Subject: Re: [PATCH v1] wdt: nuvoton: add expire function for generic reset > > On 13.09.22 08:19, Jim Liu wrote: > > Add expire_now function for generic sysreset request > > > > Signed-off-by: Jim Liu <JJLIU0(a)nuvoton.com> > > --- > > drivers/watchdog/npcm_wdt.c | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/drivers/watchdog/npcm_wdt.c b/drivers/watchdog/npcm_wdt.c > > index 256020f5d3..e56aa0ebe1 100644 > > --- a/drivers/watchdog/npcm_wdt.c > > +++ b/drivers/watchdog/npcm_wdt.c > > @@ -75,6 +75,11 @@ static int npcm_wdt_reset(struct udevice *dev) > > return 0; > > } > > > > +static int npcm_wdt_expire_now(struct udevice *dev, ulong flags) { > > + return npcm_wdt_reset(dev); > > +} > > + > > Does this really work? You are calling the watchdog reset function here in the expire function, which will just reset / trigger the WDT. I would not expect that this will expire the WDT and result in a CPU / SoC reset. > > Thanks, > Stefan > > > static int npcm_wdt_of_to_plat(struct udevice *dev) > > { > > struct npcm_wdt_priv *priv = dev_get_priv(dev); @@ -87,6 +92,7 @@ > > static int npcm_wdt_of_to_plat(struct udevice *dev) > > } > > > > static const struct wdt_ops npcm_wdt_ops = { > > + .expire_now = npcm_wdt_expire_now, > > .start = npcm_wdt_start, > > .reset = npcm_wdt_reset, > > .stop = npcm_wdt_stop, > > Viele Grüße, > Stefan Roese > > -- > DENX Software Engineering GmbH, Managing Director: Wolfgang Denk > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr(a)denx.de > ________________________________ > ________________________________ > The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.

2 2

[PATCH v6 0/8] Add support for cyclic function execution infrastruture
by Stefan Roese 15 Sep '22

15 Sep '22

This patchset adds the basic infrastructure to periodically execute code, e.g. all 100ms. Examples for such functions might be LED blinking etc. The functions that are hooked into this cyclic list should be small timewise as otherwise the execution of the other code that relies on a high frequent polling (e.g. UART rx char ready check) might be delayed too much. This patch also adds the Kconfig option CONFIG_CYCLIC_MAX_CPU_TIME_US, which configures the max allowed time for such a cyclic function. If it's execution time exceeds this time, this cyclic function will get removed from the cyclic list. How is this cyclic functionality executed? This patchset integrates the main function responsible for calling all registered cyclic functions cyclic_run() into the common WATCHDOG_RESET macro. This guarantees that cyclic_run() is executed very often, which is necessary for the cyclic functions to get scheduled and executed at their configured periods. This cyclic infrastructure will be used by a board specific function on the NIC23 MIPS Octeon board, which needs to check periodically, if a PCIe FLR has occurred. Ideas how to continue: One idea is to rename WATCHDOG_RESET to something like SCHEDULE and move the watchdog_reset call into this cyclic infrastructure as well. Or to perhaps move the shell UART RX ready polling to a cyclic function. It's also possible to extend the "cyclic" command, to support the creation of periodically executed shell commands (for testing etc). Here the Azure build, without any issues: https://dev.azure.com/sr0718/u-boot/_build/results?buildId=256&view=results Aaron Williams (1): mips: octeon_nic23: Add PCIe FLR fixup via cyclic infrastructure Stefan Roese (7): time: Import time_after64() and friends from Linux cyclic: Add basic support for cyclic function execution infrastruture cyclic: Integrate cyclic infrastructure into WATCHDOG_RESET cyclic: Integrate cyclic functionality at bootup in board_r/f cyclic: Add 'cyclic list' and 'cyclic demo' commands cyclic: Add documentation cyclic: Add a simple test MAINTAINERS | 7 + board/Marvell/octeon_nic23/board.c | 197 +++++++++++++++++++++++++++++ cmd/Kconfig | 16 +++ cmd/Makefile | 1 + cmd/cyclic.c | 84 ++++++++++++ common/Kconfig | 20 +++ common/Makefile | 1 + common/board_f.c | 2 + common/board_r.c | 2 + common/cyclic.c | 123 ++++++++++++++++++ configs/octeon_nic23_defconfig | 3 + doc/develop/cyclic.rst | 50 ++++++++ doc/develop/index.rst | 1 + doc/usage/cmd/cyclic.rst | 45 +++++++ doc/usage/index.rst | 1 + fs/cramfs/uncompress.c | 2 +- include/asm-generic/global_data.h | 7 + include/cyclic.h | 138 ++++++++++++++++++++ include/time.h | 19 +++ include/watchdog.h | 23 +++- test/common/Makefile | 1 + test/common/cyclic.c | 35 +++++ test/test-main.c | 3 + 23 files changed, 777 insertions(+), 4 deletions(-) create mode 100644 cmd/cyclic.c create mode 100644 common/cyclic.c create mode 100644 doc/develop/cyclic.rst create mode 100644 doc/usage/cmd/cyclic.rst create mode 100644 include/cyclic.h create mode 100644 test/common/cyclic.c -- 2.37.3

3 14

[PATCH] imx8mq_evk: enlarge SYS_MALLOC_F_LEN
by Peng Fan (OSS) 15 Sep '22

15 Sep '22

From: Peng Fan <peng.fan(a)nxp.com> There is "alloc space exhausted" with DEBUG_UART enabled with the options enabled. CONFIG_DEBUG_UART_BASE=0x30860000 # for uart1 CONFIG_DEBUG_UART_CLOCK=24000000 It is because CONFIG_SYS_MALLOC_F_LEN is too small, enlarge it. And set CONFIG_SPL_STACK to 0x188000 to not waste the top 16bytes. Reported-by: Heiko Thiery <heiko.thiery(a)gmail.com> Signed-off-by: Peng Fan <peng.fan(a)nxp.com> --- configs/imx8mq_evk_defconfig | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/configs/imx8mq_evk_defconfig b/configs/imx8mq_evk_defconfig index cf207295e54..d877a1290f9 100644 --- a/configs/imx8mq_evk_defconfig +++ b/configs/imx8mq_evk_defconfig @@ -2,6 +2,8 @@ CONFIG_ARM=y CONFIG_ARCH_IMX8M=y CONFIG_SYS_TEXT_BASE=0x40200000 CONFIG_SYS_MALLOC_LEN=0x600000 +CONFIG_SYS_MALLOC_F_LEN=0x10000 +CONFIG_SPL_SYS_MALLOC_F_LEN=0x2000 CONFIG_SPL_GPIO=y CONFIG_SPL_LIBCOMMON_SUPPORT=y CONFIG_SPL_LIBGENERIC_SUPPORT=y @@ -36,7 +38,7 @@ CONFIG_SPL_BSS_START_ADDR=0x180000 CONFIG_SPL_BSS_MAX_SIZE=0x2000 CONFIG_SPL_BOARD_INIT=y # CONFIG_SPL_SHARES_INIT_SP_ADDR is not set -CONFIG_SPL_STACK=0x187ff0 +CONFIG_SPL_STACK=0x188000 CONFIG_SYS_SPL_MALLOC=y CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x42200000 -- 2.36.0

4 5

[PATCH] image: Ensure image header name is null terminated
by Joel Stanley 15 Sep '22

15 Sep '22

When building with GCC 12: ../include/image.h:779:9: warning: ‘strncpy’ specified bound 32 equals destination size [-Wstringop-truncation] 779 | strncpy(image_get_name(hdr), name, IH_NMLEN); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ensure the copied string is null terminated by always setting the final byte to 0. Shorten the strncpy to IH_NMLEN-1 as we will always overwrite the last byte. We can't use strlcpy as this is code is built on the host as well as the target. Fixes: b97a2a0a21f2 ("[new uImage] Define a API for image handling operations") Signed-off-by: Joel Stanley <joel(a)jms.id.au> --- include/image.h | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/include/image.h b/include/image.h index e4c6a50b885f..665b2278b7fb 100644 --- a/include/image.h +++ b/include/image.h @@ -776,7 +776,10 @@ image_set_hdr_b(comp) /* image_set_comp */ static inline void image_set_name(image_header_t *hdr, const char *name) { - strncpy(image_get_name(hdr), name, IH_NMLEN); + char *hdr_name = image_get_name(hdr); + + strncpy(hdr_name, name, IH_NMLEN - 1); + hdr_name[IH_NMLEN - 1] = '\0'; } int image_check_hcrc(const image_header_t *hdr); -- 2.35.1

6 6

Pull request for efi next
by Heinrich Schuchardt 14 Sep '22

14 Sep '22

Dear Tom, please, pull into the next branch. The following changes since commit c2238fcf0c4567bbd581882e5952047e71406f58: Merge branch '2022-09-13-add-aspeed-spi-controller' into next (2022-09-13 15:55:33 -0400) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-efi.git tags/efi-next-2022-09-14 for you to fetch changes up to da4fb707ca095c223b67637e2525df4866e51c62: test: unit test for eficonfig (2022-09-14 08:43:32 +0200) Gitlab CI showed no issues: https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/13439 ---------------------------------------------------------------- Pull request for efi next UEFI: Implement a command eficonfig to maintain Load Options and boot order via menus. ---------------------------------------------------------------- Masahisa Kojima (10): eficonfig: menu-driven addition of UEFI boot option eficonfig: add "Edit Boot Option" menu entry menu: add KEY_PLUS, KEY_MINUS and KEY_SPACE handling eficonfig: add "Delete Boot Option" menu entry bootmenu: add removable media entries eficonfig: scan media device in eficonfig startup eficonfig: add "Change Boot Order" menu entry doc:bootmenu: add description for UEFI boot support doc:eficonfig: add documentation for eficonfig command test: unit test for eficonfig cmd/Kconfig | 7 + cmd/Makefile | 1 + cmd/bootmenu.c | 22 +- cmd/eficonfig.c | 2502 ++++++++++++++++++++++++ common/menu.c | 9 + configs/sandbox_defconfig | 1 + doc/usage/cmd/bootmenu.rst | 74 + doc/usage/cmd/eficonfig.rst | 71 + doc/usage/index.rst | 1 + include/efi_config.h | 98 + include/efi_loader.h | 53 + include/menu.h | 3 + lib/efi_loader/efi_bootmgr.c | 7 + lib/efi_loader/efi_boottime.c | 52 +- lib/efi_loader/efi_console.c | 70 + lib/efi_loader/efi_disk.c | 50 + lib/efi_loader/efi_file.c | 75 +- test/py/tests/test_eficonfig/conftest.py | 40 + test/py/tests/test_eficonfig/test_eficonfig.py | 354 ++++ 19 files changed, 3437 insertions(+), 53 deletions(-) create mode 100644 cmd/eficonfig.c create mode 100644 doc/usage/cmd/eficonfig.rst create mode 100644 include/efi_config.h create mode 100644 test/py/tests/test_eficonfig/conftest.py create mode 100644 test/py/tests/test_eficonfig/test_eficonfig.py

2 1

[PATCH 1/1] doc: improve description of autostart
by Heinrich Schuchardt 14 Sep '22

14 Sep '22

Complete the list of commands influenced by the autostart environment variable. Make it clearer what values qualifies at 'yes'. Eventually the list of environment variables to be alphabetically sorted. Move autostart up. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt(a)canonical.com> --- doc/usage/environment.rst | 34 +++++++++++++++++++++------------- 1 file changed, 21 insertions(+), 13 deletions(-) diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst index 561076bac9..7906ace2af 100644 --- a/doc/usage/environment.rst +++ b/doc/usage/environment.rst @@ -106,6 +106,27 @@ many cases the value in the default environment comes from a CONFIG option - see This is most-likely not complete: +autostart + If set to "yes" (actually any string starting with 1, y, Y, t, or T) an + image loaded with one of the commands listed below will be automatically + started by internally invoking the bootm command. + + * bootelf - Boot from an ELF image in memory + * bootp - boot image via network using BOOTP/TFTP protocol + * dhcp - boot image via network using DHCP/TFTP protocol + * diskboot - boot from ide device + * nboot - boot from NAND device + * nfs - boot image via network using NFS protocol + * rarpboot - boot image via network using RARP/TFTP protocol + * scsiboot - boot from SCSI device + * tftpboot - boot image via network using TFTP protocol + * usbboot - boot from USB device + + If the environment variable autostart is not set to a value starting with + 1, y, Y, t, or T, an image passed to the "bootm" command will be copied to + the load address (and eventually uncompressed), but NOT be started. + This can be used to load and uncompress arbitrary data. + baudrate Used to set the baudrate of the UART - it defaults to CONFIG_BAUDRATE (which defaults to 115200). @@ -174,19 +195,6 @@ autoload configuration from the BOOTP server, but not try to load any image. -autostart - if set to "yes", an image loaded using the "bootp", "dhcp", - "rarpboot", "tftpboot" or "diskboot" commands will - be automatically started (by internally calling - "bootm") - - If unset, or set to "1"/"yes"/"true" (case insensitive, just the first - character is enough), a standalone image - passed to the "bootm" command will be copied to the load address - (and eventually uncompressed), but NOT be started. - This can be used to load and uncompress arbitrary - data. - fdt_high if set this restricts the maximum address that the flattened device tree will be copied into upon boot. -- 2.37.2

2 1

[PATCH 0/8] image: Refactor ramdisk code to avoid #ifdef
by Simon Glass 14 Sep '22

14 Sep '22

The previous attempt at this[1] broke a board and was reverted in [2]. This series adopts a slightly different approach, splitting the changes into many commits. [1] f33a2c1bd0f ("image: Remove #ifdefs from select_ramdisk()") [2] 621158d106f ("Revert "image: Remove #ifdefs from select_ramdisk()"") Simon Glass (8): image: Fix up ANDROID_BOOT_IMAGE ramdisk code image: Track when ramdisk processing is completed image: Drop #ifdefs for LEGACY_IMAGE_FORMAT image: Drop one #ifdef for FIT image: Drop another #ifdef for FIT image: Drop remaining FIT #ifdef image: Correct indentation in select_ramdisk() image: Drop some other #ifdefs in image-board.c boot/image-board.c | 212 ++++++++++++++++++++++++--------------------- include/image.h | 6 ++ 2 files changed, 121 insertions(+), 97 deletions(-) -- 2.37.2.672.g94769d06f0-goog

3 11