- Oct 09, 2021
-
-
Anatolij Gustschin authored
After DM_VIDEO conversion the 'vidconsole' is the correct name for the frame buffer console. 'video' will not work, so update the description of the config option. Signed-off-by:
Anatolij Gustschin <agust@denx.de>
-
At present U-Boot has a header file called lz4.h for its own use. If the host has its own lz4 header file installed (e.g. from the 'liblz4-dev' package) then host builds will use that instead. Move the U-Boot file into its own directory, as is done with various other headers with the same problem. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Oct 08, 2021
-
-
This function is far too long. Before trying to remove #ifdefs, split out the code that deals with selecting the FDT into a separate function. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Move the variables declarations to where they are needed, to reduce the number of #ifdefs needed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Drop the #ifdefs which are easy to remove without refactoring. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Use boolean variables to deal with the strange #ifdef logic of this function, so we can remove the #ifdefs. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This function is far too long. Before trying to remove #ifdefs, split out the code that deals with selecting the ramdisk into a separate function. Leave the code indented as it was for easier review. The next patch cleans this up along with checkpatch violations. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Move the variables declarations to where they are needed, to reduce the number of #ifdefs needed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Remove ifdefs in this file, so far as possible without too much refactoring. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Use a simple return to drop the unwanted code. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This function is only used in one place and does not need to use the preprocessor. Move it to the C file and convert it to a normal function. Drop fit_unsupported() since it is not used. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
We can use the new host_build() function for this, so drop it. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
This is not needed with Kconfig, since we can use IS_ENABLED() easily enough. Drop it. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
This is not needed with Kconfig, since we can use IS_ENABLED() easily enough. Drop it. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
This is not needed with Kconfig, since we can use IS_ENABLED() easily enough and the board code is now in a separate file. Update the only place where this is used and drop it. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
Add a host Kconfig for CRC32. With this we can use CONFIG_IS_ENABLED(CRC32) directly in the host build, so drop the unnecessary indirection. Add a few more conditions to SPL_CRC32 to avoid build failures as well as TPL_CRC32. Also update hash.c to make crc32 optional and to actually take notice of SPL_CRC32. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
Add a host Kconfig for OF_LIBFDT. With this we can use CONFIG_IS_ENABLED(OF_LIBFDT) directly in the tools build, so drop the unnecessary indirection. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
Make use of the host Kconfig for FIT. With this we can use CONFIG_IS_ENABLED(FIT) directly in the host build, so drop the unnecessary indirection. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
We can use the __maybe_unused attribute to avoid some of the #ifdefs in this file. Update the functions accordingly. Note: The actual hashing interface is still a mess, with four separate combinations and lots of #ifdefs. This should really use a driver approach, e.g. as is done with partition drivers. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
At present when building host tools, we force CONFIG_SHAxxx to be enabled regardless of the board Kconfig setting. This is done in the image.h header file. For SPL we currently just assume the algorithm is desired if U-Boot proper enables it. Clean this up by adding new Kconfig options to enable hashing on the host, relying on CONFIG_IS_ENABLED() to deal with the different builds. Add new SPL Kconfigs for hardware-accelerated hashing, to maintain the current settings. This allows us to drop the image.h code and the I_WANT_MD5 hack. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
In preparation for enabling CONFIG_IS_ENABLED() on the host build, add some options to enable the various FIT options expected in these tools. This will ensure that the code builds correctly when CONFIG_TOOLS_xxx is distinct from CONFIG_xxx. Drop some #ifdefs which are immediately unnecessary (many more are in later patches). Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
With the new TOOLS_LIBCRYPTO and some other changes, it seems that we are heading towards calling this a tools build rather than a host build, although of course it does happen on the host. I cannot think of anything built by the host which cannot be described as a tool, so rename this function. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com>
-
Drop some more ifdefs in image-board.c and also the FPGA part of bootm.c which calls into it. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add a macro to handle manually relocating a pointer. Update the iamge code to use this to avoid needing #ifdefs. This also fixes a bug where the 'done' flag was not set. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Rather than adding an #ifdef and open-coding this calculation, add a helper function to handle it. Use this in the image code. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
To avoid having #ifdefs in a few functions which are completely different in the board and host code, create a new image-host.c file. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Tidy up the warnings. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
To avoid a large #ifdef in the image.c file, move the affected code into a separate file. Avoid any style fix-ups for easier review. Those are in the next patch. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Adjust this function so that preprocessor macros are not needed. With this, the host build uses more of the same header files as the target build. Rather than definining CONFIG_SYS_MALLOC_LEN, add a CONSERVE_MEMORY define, since that is the purpose of the value. This appears to have no impact on code size from a spot check of a few boards (snow, firefly-rk3288, boston32r2el, m53menlo). Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The zstd implementation prints the error in image_decomp() which is incorrect and does not match other algorithms. Drop this and let the caller report the error. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
At present this function is full of preprocessor macros. Adjust it to check for an unsupported algorithm after the switch(). This will allow us to drop the macros. Fix up the return-value path and an extra blank line while we are here. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The existing zstd API requires the same sequence of calls to perform its task. Create a helper for U-Boot, to avoid code duplication, as is done with other compression algorithms. Make use of of this from the image code. Note that the zstd code lacks a test in test/compression.c and this should be added by the maintainer. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Oct 07, 2021
-
-
cherry-picked from NXP code: 719d665a87c6: ("MLK-20467 imx8m: Fix issue for booting signed image through uuu") which fixes secure boot on imx8m based boards. Problem was that FIT header and so IVT header too, was loaded to memallocated address. So the ivt header address coded in IVT itself does not fit with the real position. Signed-off-by:
Heiko Schocher <hs@denx.de> Tested-by:
Tim Harvey <tharvey@gateworks.com>
-
add hook function spl_load_simple_fit_fix_load() which is called after fit image header is loaded. Signed-off-by:
Heiko Schocher <hs@denx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Samuel Holland authored
bootm_low is used as a base address is used to allocate space for the FDT blob, initrd, cmdline, etc. when booting Linux. Set the default value for RISC-V to the start of the first DRAM bank, so platforms can get their DRAM layout from the device tree, and do not need to define CONFIG_SYS_SDRAM_BASE. Signed-off-by:
Samuel Holland <samuel@sholland.org> Reviewed-by:
Leo Yu-Chi Liang <ycliang@andestech.com>
-
- Oct 05, 2021
-
-
The configuration CONFIG_OPTEE is defined 2 times: 1- in lib/optee/Kconfig for support of OPTEE images loaded by bootm command 2- in drivers/tee/optee/Kconfig for support of OP-TEE driver. It is abnormal to have the same CONFIG define for 2 purpose; and it is difficult to managed correctly their dependencies. Moreover CONFIG_SPL_OPTEE is defined in common/spl/Kconfig to manage OPTEE image load in SPL. This definition causes an issue with the macro CONFIG_IS_ENABLED(OPTEE) to test the availability of the OP-TEE driver. This patch cleans the configuration dependency with: - CONFIG_OPTEE_IMAGE (renamed) => support of OP-TEE image in U-Boot - CONFIG_SPL_OPTEE_IMAGE (renamed) => support of OP-TEE image in SPL - CONFIG_OPTEE (same) => support of OP-TEE driver in U-Boot - CONFIG_OPTEE_LIB (new) => support of OP-TEE library After this patch, the macro have the correct behavior: - CONFIG_IS_ENABLED(OPTEE_IMAGE) => Load of OP-TEE image is supported - CONFIG_IS_ENABLED(OPTEE) => OP-TEE driver is supported Signed-off-by:
Patrick Delaunay <patrick.delaunay@foss.st.com>
-
- Sep 30, 2021
-
-
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Signed-off-by:
Wolfgang Denk <wd@denx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Sep 28, 2021
-
-
Tom Rini authored
We have individual SOC symbols for each keystone 2 platform. Use the existing CONFIG_ARCH_KEYSTONE rather than CONFIG_SOC_KEYSTONE to encompass all of the keystone families. Signed-off-by:
Tom Rini <trini@konsulko.com>
-