- Feb 09, 2023
-
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_NVEDIT_EFI defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_NET defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 6 usages of this option to the non-SPL form, since there is no SPL_CMD_MMC defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_MBR defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_HASH defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_FRU defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_CMD_FDT defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_ERASEENV defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_CMD_EFICONFIG defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 7 usages of this option to the non-SPL form, since there is no SPL_CMD_CLK defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Sean Anderson <seanga2@gmail.com>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_BOOTZ defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_CMD_BOOTM_PRE_LOAD defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_BOOTI defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_BCB defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_BOOTSTAGE_REPORT defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_BOOTSTAGE_FDT defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_BNXT_ETH defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_ARMADA_8K defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_ARMADA_3700 defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_ARCH_ZYNQ defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 2 usages of this option to the non-SPL form, since there is no SPL_ALLEYCAT_5 defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_AHCI defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_A003399_NOR_WORKAROUND defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Fix a typo in a comment. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
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:
Tom Rini <trini@konsulko.com>
-
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:
Simon Glass <sjg@chromium.org> Reviewed-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 <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
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 <trini@konsulko.com>
-
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:
Simon Glass <sjg@chromium.org>
-
This is not used anymore. Drop the driver and Kconfig option. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
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:
Simon Glass <sjg@chromium.org>
-
This is not used. Drop the driver and Kconfig option. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This option is not defined anywhere. Drop it. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This is not used. Drop the driver and Kconfig option. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This is not used. Drop the driver and Kconfig option. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This is not used. Drop the driver and Kconfig option. Signed-off-by:
Simon Glass <sjg@chromium.org>
-