- Feb 10, 2023
-
-
The change boot order menu in eficonfig can have at most INT_MAX lines and it is troublesome to scroll down to the "Save" entry. This commit assigns CTRL+S to save the boot order. Signed-off-by:
Masahisa Kojima <masahisa.kojima@linaro.org> Acked-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
On the sandbox called without "--terminal raw" CTRL+C leaves U-Boot, "ESC/CTRL+C to quit" is misleading. Let's remove CTRL+C to quit key handling from bootmenu and eficonfig menu. Signed-off-by:
-
Current U-Boot implements 64-bit boundary for efi_guid_t structure. It follows the UEFI specification, page 21 of the UEFI Specification v2.10 says about EFI_GUID: 128-bit buffer containing a unique identifier value. Unless otherwise specified, aligned on a 64-bit boundary. On the other hand, page 163 of the UEFI specification v2.10 and EDK2 reference implementation both define EFI_GUID as struct { u32 a; u16; b; u16 c; u8 d[8]; }; and so the implied alignment is 32-bit not 64-bit like U-Boot efi_guid_t. Due to this alignment difference, EDK2 application "CapsuleApp.efi -P" does not work as expected. This calls EFI_FIRMWARE_MANAGEMENT_PROTOCOL.GetImageInfo() and dump the EFI_FIRMWARE_IMAGE_DESCRIPTOR structure, offsetof(EFI_FIRMWARE_IMAGE_DESCRIPTOR, ImageTypeId) is different, 8 in U-Boot and 4 in EDK2(CapsuleApp.efi). Here is the wrong EFI_GUID dump. wrong dump : ImageTypeId - 00000000-7D83-058B-D550-474CA19560D8 expected : ImageTypeId - 058B7D83-50D5-4C47-A195-60D86AD341C4 EFI_FIRMWARE_IMAGE_DESCRIPTOR structure is defined in UEFI specification: typedef struct { UINT8 ImageIndex; EFI_GUID ImageTypeId; UINT64 ImageId <snip> } EFI_FIRMWARE_IMAGE_DESCRIPTOR; There was the relevant patch for linux kernel to use 32-bit alignment for efi_guid_t [1]. U-Boot should get aligned to EDK2 reference implementation and linux kernel. Due to this alignment change, efi_hii_ref structure in include/efi_api.h is affected, but it is not used in the current U-Boot code. [1] https://lore.kernel.org/all/20190202094119.13230-5-ard.biesheuvel@linaro.org/ Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org> Signed-off-by:Ilias Apalodimas <ilias.apalodimas@linaro.org>
-
Talks are a great way to learn about U-Boot and have been lost now that the Denx Wiki has gone away. These are stored at elinux.org so link to that . Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Sean Anderson <seanga2@gmail.com>
-
Heinrich Schuchardt authored
Add missing information to the configuration section of the setexpr man-page. Signed-off-by:
-
Heinrich Schuchardt authored
Device name are typically longer than 8 characters. This leads to ragged output. Only the I and O bit of the device flags are of interest for the user. Writing a hexadecimal number is just confusing. Before the patch the output looked like this: => coninfo List of available devices: pl011@9000000 00000007 IO stdin stdout stderr serial 00000003 IO usbkbd 00000001 I. With the patch the output looks like this: => coninfo List of available devices |-- pl011@9000000 (IO) | |-- stdin | |-- stdout | |-- stderr |-- serial (IO) |-- usbkbd (I) Signed-off-by: -
Heinrich Schuchardt authored
The readme file for buildman is called buildman.rst. Signed-off-by:
-
- Feb 09, 2023
-
-
Tom Rini authored
- Update the socrates env to be plain text, and fix the issue of CONFIG_MMC_QUIRKS not being applied within SPL, leading to some boot failures.
-
as Tom suggested get rid of CFG_EXTRA_ENV_SETTINGS and enable CONFIG_ENV_SOURCE_FILE and use text file board/socrates/socrates.env which contains the default environment. While at it, cleanup the default Environment. Signed-off-by:
Heiko Schocher <hs@denx.de> Suggested-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_MMC_QUIRKS defined in Kconfig Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
- Feb 08, 2023
-
-
Tom Rini authored
- Correct my mistake with defaulting to not setting LMB_USE_MAX_REGIONS, and fix the lmb test to scale with more than 8 regions before setting the new default to 16 regions. This doesn't strictly fix all issues, but puts us ahead of where we were.
-
Since commit 06d514d7 ("lmb: consider EFI memory map") the EFI regions are also pushed into the lmb if EFI_LOADER is enabled (which is by default on most system). Which can cause the number of entries to go over the maximum as it's default is only 8. Specifically i ran into this case on an TI am62 which has an fdt with 4 reserved regions (in practice 3 lmb entries due to adjecent ranges). As this is likely to impact more devices bump the default max regions to 16 so there is a bit more slack. Fixes: 06d514d7 ("lmb: consider EFI memory map") Link: https://bugzilla.opensuse.org/show_bug.cgi?id=1207562 Reviewed-by:
Francesco Dolcini <francesco.dolcini@toradex.com> Signed-off-by:
Sjoerd Simons <sjoerd@collabora.com> Signed-off-by:
Michal Suchanek <msuchanek@suse.de> [trini: collect tags from the other equivalent patch]
-
Tom Rini authored
First, this test depends on CONFIG_LMB_USE_MAX_REGIONS, so add that as a test before building. Second, instead of using a hard-coded value of 8, which is the default of CONFIG_LMB_USE_MAX_REGIONS previously, use that directly and update the comments. The only trick here is that one part of the test itself also was written with the value of 8 itself in mind. Rework the size of the lmb region we allocate to scale with the value of CONFIG_LMB_USE_MAX_REGIONS. Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
-
Tom Rini authored
As explained by Philippe Schenker, I was misinterpreting what happened in the case where we do not set LMB_USE_MAX_REGIONS and so had re-introduced the problem I was attempting to more widely resolve. This reverts commit 007ae5d1. Reported-by:
Philippe Schenker <philippe.schenker@toradex.com> Signed-off-by:
-
Tom Rini authored
To quote the author: This series adds source scanning to moveconfig.py so that it can look for Kconfig options mentioned in the source which do not appear in Kconfig, and vice versa. This tool is then used to clean up the unused or obsolete options mentioned in Makefiles, along with any attached source code.
-
- Feb 07, 2023
-
-
These are only present in SPL. Drop the references to non-SPL versions. Signed-off-by: -
This is not used anymore. Drop the driver and Kconfig option. Signed-off-by: -
This is very old and does not appear to be used. The CONFIG option enabling it is no-longer present. Drop it. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by: -
This option is not defined anywhere. Drop it. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by: -
This is not used and appears to be associated with the faraday board which has been removed. Drop the driver and Kconfig options. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by: -
These are not used. Drop the drivers and Kconfig option. Also drop an old declaration in the netdev.h header. Signed-off-by: -
CONFIG_UBOOT_PAD_TO is not defined anywhere. Drop this dead code. Signed-off-by:
Stefan Roese <sr@denx.de>
-
This option as well as CONFIG_TARGET_P1022DS and CONFIG_TARGET_P5020DS are not defined anywhere. Drop them. Signed-off-by: -
This option is not defined anywhere. Drop it. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by:
-
This is not used since CONFIG_SYS_FPGA_COMMON is not defined anywhere. Drop the code and the Makefile rule. Signed-off-by: -
The SPL_TPL part is in the wrong place. Fix it. Signed-off-by:
Claudiu Beznea <claudiu.beznea@microchip.com>
-
This seems to have been used by ppc4xx which was removed a while back. The Kconfig does not exist so it is never built. Drop it. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by: -
This option does not exist, so the code attached to it is not used. Drop it. Signed-off-by: -
This is not used since this commit: 76386d61 arm: Remove cm_t35 board Drop the driver and Kconfig option. Signed-off-by:
-
This option does not exist, so the Makefile rule does nothing. Drop it. Signed-off-by: -
These drivers are not used and have not been converted to driver model. Drop them and references to the non-existent CONFIG options they use. Signed-off-by: -
This has been renamed to CONFIG_ARCH_RMOBILE but this one was left behind. It doesn't point to a directory that exists, so just drop it. Signed-off-by: -
This is not used. Drop the driver and Kconfig option. Signed-off-by:
-
