u-boot.git/cmd, branch v2021.07-rc4

efi_loader: simplify accessing variables

2021-05-25T11:06:58Z

Use efi_get_variable_int() instead of EFI_CALL(RT->get_variable()). Use efi_set_variable_int() instead of EFI_CALL(efi_set_variable()). Signed-off-by: Heinrich Schuchardt Tested-by: Ilias Apalodimas Reviewed-by: Ilias Apalodimas

efi_loader: use efi_create_indexed_name()

2021-05-25T11:06:58Z

Simplify the creation of indexed variable names like 'Boot0000' by using function efi_create_indexed_name(). Signed-off-by: Heinrich Schuchardt Reviewed-by: Ilias Apalodimas

efi_loader: simplify show_efi_boot_order()

2021-05-25T11:06:58Z

To print a UTF-16 string use %ls instead of converting string to UTF-8. Signed-off-by: Heinrich Schuchardt Reviewed-by: Ilias Apalodimas

efi_loader: simplify show_efi_boot_opt_data()

2021-05-25T11:06:58Z

To print a UTF-16 string use %ls instead of converting string to UTF-8. Signed-off-by: Heinrich Schuchardt Reviewed-by: Ilias Apalodimas

stackprot: Make our test a bit more complex

2021-05-24T18:23:01Z

With better compiler optimizations available, a compiler may see we do nothing with our buffer after calling memset and omit the call, thus causing us to not smash the stack. Add a comment to explain why we now also have a printf call, so that the test will pass as the memset will not be omitted. Reported-by: Marek Behún Signed-off-by: Tom Rini

cmd: mvebu: Rename rx_training to mvebu_comphy_rx_training

2021-05-16T04:48:45Z

Rename the misleading cmd "rx_training" to "mvebu_comphy_rx_training" to avoid confusion and mixup with DDR3/4 training. This makes it clear, that this command is platform specific and handles the COMPHY RX training. Also depend this cmd on ARMADA_8K and not TARGET_MVEBU_ARMADA_8K to make is available for OcteonTX2 CN913x. Signed-off-by: Stefan Roese Cc: Pali Rohár Cc: Marek Behun Cc: Kostya Porotchkin Cc: Nadav Haklai Acked-by: Marek Behún Acked-by: Pali Rohár

cmd: add support for a new "extension" command

2021-05-13T17:09:05Z

This patch adds a new "extension" command, which aims at detecting extension boards connected to the hardware platform, and apply the Device Tree overlays that describe the hardware present on those extension boards. In order to enable this mechanism, board-specific code must implement the extension_board_scan() function that fills in a linked list of "struct extension", each describing one extension board. In addition, the board-specific code must select the SUPPORT_EXTENSION_SCAN Kconfig boolean. Based on this: - "extension scan" makes the generic code call the board-specific extension_board_scan() function to retrieve the list of detected extension boards. - "extension list" allows to list the detected extension boards. - "extension apply |all" allows to apply the Device Tree overlay(s) corresponding to one, or all, extension boards The latter requires two environment variables to exist and set one variable to run: - extension_overlay_addr: the RAM address where to load the Device Tree overlays - extension_overlay_cmd: the U-Boot command to load one overlay. Indeed, the location and mechanism to load DT overlays is very setup specific. - extension_overlay_name: set by the command: the name of the DT which will be load during the execution. When calling the command described in the extension_overlay_cmd variable, the variable extension_overlay_name will be defined. So a typical extension_overlay_cmd will look like this: extension_overlay_cmd=load mmc 0:1 $extension_overlay_addr /boot/$extension_overlay_name Here is an example on how to use it: => run loadfdt => fdt addr $fdtaddr => setenv extension_overlay_addr 0x1000 => setenv extension_overlay_cmd 'load mmc 0:1 ${extension_overlay_addr} /boot/${extension_overlay_name}' => extension scan Found 1 extension board(s). => extension apply 0 519 bytes read in 3 ms (168.9 KiB/s) Signed-off-by: Kory Maincent Reviewed-by: Maxime Ripard

fdt_support: move fdt_valid from cmd_fdt.c to fdt_support.c

2021-05-13T11:19:34Z

Move the fdt_valid function to fdt_support. This changes allow to be able to test the validity of a devicetree in other c files. Update code syntax. Signed-off-by: Kory Maincent Reviewed-by: Tom Rini Reviewed-by: Maxime Ripard

x86: Correct regwidth prompt in cbsysinfo

2021-05-10T05:56:12Z

This should be 'regwidth', not 'baud'. Fix it. Signed-off-by: Simon Glass Reviewed-by: Bin Meng

Merge https://source.denx.de/u-boot/custodians/u-boot-riscv

2021-05-07T12:57:32Z