- Sep 02, 2022
-
-
Some tests can have race conditions which are hard to detect on a single one. Add a way to run tests more than once, to help with this. Each individual test is run the requested number of times before moving to the next test. If any runs failed, a message is shown. This is most useful when running a single test, since running all tests multiple times can take a while. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
LTO (Link-Time Optimisation) is an very useful feature which can significantly reduce the size of U-Boot binaries. So far it has been made available for selected ARM boards and sandbox. However, incremental builds are much slower when LTO is used. For example, an incremental build of sandbox takes 2.1 seconds on my machine, but 6.7 seconds with LTO enabled. Add a NO_LTO parameter to the build, similar to NO_SDL, so it can be disabled during development if needed, for faster builds. Add some documentation about LTO while we are here. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This command is being introduced with the goal of allowing user-friendly "generic use case" U-Boot builds to pause until user input under some situations. The main use case would be when a boot failure happens, to pause until the user has had time to acknowledge the current state. Tested using: make && ./u-boot -v -T -c 'ut lib lib_test_hush_pause' Signed-off-by:
Samuel Dionne-Riel <samuel@dionne-riel.com> Cc: Simon Glass <sjg@chromium.org>
-
- Aug 26, 2022
-
-
Since both pm8916.c and pm8916_gpio.c are already supporting multiple Qcom SoCs, it makes sense to rename these drivers to pmic_qcom.c and qcom_pmic_gpio.c respectively. Also, these driver can be extended to support additional functionality if required for other Qcom SoCs. Along with this import latest DT binding: qcom,spmi-pmic.txt from Linux kernel and thereby remove pm8916.txt. Signed-off-by:
Sumit Garg <sumit.garg@linaro.org>
-
- Aug 22, 2022
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 21, 2022
-
-
Tom Rini authored
These boards have been orphaned for some time and are behind on various DM migrations. Remove them. Cc: Priyanka Jain <priyanka.jain@nxp.com> Cc: Peng Fan <peng.fan@nxp.com> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 20, 2022
-
-
Explain when devices should get activated. Signed-off-by:
Michal Suchanek <msuchanek@suse.de> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Heinrich Schuchardt authored
The ELF U-Boot image produced by qemu-riscv64_smode_defconfig can be used to boot with QEMU and KVM. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
- Aug 13, 2022
-
-
This is an attempt to answer the comments provided by Xavier [1]. [1] https://lore.kernel.org/all/Yulcol7HpTHtjXTX@begut/ Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Link to patman's documentation from the doc/ directory so that it appears in the 'make htmldocs' output. Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
This was widely used by U-Boot for a long time, but is not used anymore, with Gitlab and Azure taking over. Drop the text. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
We talk about importing code from other projects in two places. The first place is in the coding style section, where we explain when to or not to deviate in terms of white space, etc. In the process documentation we now add a note about saying where the code was imported from and to ensure that you do not copy Signed-off-by or other tags. Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Sudeep Holla <sudeep.holla@arm.com> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Heinrich Schuchardt authored
Add link to usage/cmd/exception.rst. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Heinrich Schuchardt authored
* describe crashs in UEFI binaries * provide architechture specific information for the sandbox and RISC-V Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Heinrich Schuchardt authored
Provide a man-page for the gpio command. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
These typos were found while reading the docs. Signed-off-by:
Paul Barker <paul.barker@sancloud.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Heinrich Schuchardt authored
Remove alias 'efi' with invalid data. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Aug 12, 2022
-
-
Add some documentation updates, particularly about global bootmeths. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add some documentation and a new flag so that we can safely enabled using the ofnode interface to write to the device tree. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
At present ofnode only works with a single device tree, for the most part. This is the control FDT used by U-Boot. When booting an OS we may obtain a different device tree and want to modify it. Add some initial support for this into the ofnode API. Note that we don't permit aliases in this other device tree, since the of_access implementation maintains a list of aliases collected at start-up. Also, we don't need aliases to do fixups in the other FDT. So make sure that flat tree and live tree processing are consistent in this area. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The unflattening algorithm results in a single block of memory being allocated for the whole tree. When writing new properties, these are allocated new memory outside that block. When the block is freed, the allocated properties remain. Document how this works and the potential memory leak, as well as mentioning that updating the livetree is actually supported now. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add a few links to documents about Verified Boot for Embedded (VBE). These will be expanded as development proceeds. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Aug 09, 2022
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 05, 2022
-
-
This is not needed now that CONFIG_SYS_TARGET_NAME is correctly determined when scanning Kconfig. This reverts commit 25b8acee. Signed-off-by:
Simon Glass <sjg@chromium.org> Suggested-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- Aug 04, 2022
-
-
Tom Rini authored
There are a large number of options under CONFIG_SYS (but some of these are elsewhere, spotted while cleaning CONFIG_SYS) that are never referenced, or only used slightly later in the config file. Remove or restructure these. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 02, 2022
-
-
Add a usage document for the 'rng' u-boot command. Signed-off-by:
Sughosh Ganu <sughosh.ganu@linaro.org> Reviewed-by:
Ilias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Ilias Apalodimas <ilias.apalodimas@linaro.org>
-
- Jul 29, 2022
-
-
Start by describing in general the best practices for how to implement configuration of some aspect of U-Boot. This generally means finding the right choices for when something should be static or dynamically configured and enabled. Then further document when to use CONFIG or CFG namespaces for static configuration. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
Describe exactly which bytes are hashed and in what order when signing a configuration. Signed-off-by:
Martin Bonner <martingreybeard@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Start by elaborating on what some of our constraints tend to be with image location values, and document where these external constraints can come from. Provide a new subsection, an example based on the TI ARMv7 OMAP2PLUS families of chips, that gives sample values and explains why we use these particular values. This is based on what is in include/configs/ti_armv7_common.h as of fb3ad9bd ("TI: Add, use a DEFAULT_LINUX_BOOT_ENV environment string") as this contains just the values referenced in this document now and not some of the further additions that are less generic. Cc: Heinrich Schuchardt <xypron.glpk@gmx.de> Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
- Jul 26, 2022
-
-
Simon Glass authored
Add some information about the 'fdt addr' subcommand, to get things started. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
When CONFIG_LOG is activated, if LOG_DEBUG is defined in a file and DEBUG is not defined the trace with debug() macro are not displayed, because the parameter cond : _DEBUG = 0 is checked in debug_cond(). With this patch the define DEBUG, used to force the trace generated by debug() macro, is linked with the define LOG_DEBUG, used to force the trace generated by other macros (log_debug, dev_dbg, pr_debug). We only need to define LOG_DEBUG in a file to activate all the traces generated by any U-Boot debug macro, as it is described in /doc/develop/logging.rst Signed-off-by:
Patrick Delaunay <patrick.delaunay@foss.st.com>
-
Adrian Fiergolski authored
Add supporting new compatible string "u-boot,zynqmp-fpga-enc" to handle loading encrypted bitfiles. This feature requires encrypted FSBL, as according to UG1085: "The CSU automatically locks out the AES key, stored in either BBRAM or eFUSEs, as a key source to the AES engine if the FSBL is not encrypted. This prevents using the BBRAM or eFUSE as the key source to the AES engine during run-time applications." Signed-off-by:
Adrian Fiergolski <adrian.fiergolski@fastree3d.com> Co-developed-by:
Oleksandr Suvorov <oleksandr.suvorov@foundries.io> Signed-off-by:
Oleksandr Suvorov <oleksandr.suvorov@foundries.io> Tested-by:
Adrian Fiergolski <adrian.fiergolski@fastree3d.com> Link: https://lore.kernel.org/r/20220722141614.297383-14-oleksandr.suvorov@foundries.io Signed-off-by:
Michal Simek <michal.simek@amd.com>
-
Oleksandr Suvorov authored
Add supporting new compatible string "u-boot,zynqmp-fpga-ddrauth" to handle loading authenticated images (DDR). Based on solution by Jorge Ramirez-Ortiz <jorge@foundries.io> Signed-off-by:
Oleksandr Suvorov <oleksandr.suvorov@foundries.io> Tested-by:
Ricardo Salveti <ricardo@foundries.io> Link: https://lore.kernel.org/r/20220722141614.297383-13-oleksandr.suvorov@foundries.io Signed-off-by:
Michal Simek <michal.simek@amd.com>
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Jul 25, 2022
-
-
Add support for Qualcomm QCS404 SoC based evaluation board. Features: - Qualcomm Snapdragon QCS404 SoC - 1GiB RAM - 8GiB eMMC, uSD slot U-boot is chain loaded by ABL in 64-bit mode as part of boot.img. For detailed build and boot instructions, refer to doc/board/qualcomm/qcs404.rst. Signed-off-by:
Sumit Garg <sumit.garg@linaro.org>
-
Add support for 96Boards Dragonboard 845C aka Robotics RB3 development platform. This board complies with 96Boards Open Platform Specifications. Features: - Qualcomm Snapdragon SDA845 SoC - 4GiB RAM - 64GiB UFS drive U-boot is chain loaded by ABL in 64-bit mode as part of boot.img. For detailed build and boot instructions, refer to doc/board/qualcomm/sdm845.rst, board: dragonboard845c. Signed-off-by:
Sumit Garg <sumit.garg@linaro.org> Reviewed-by:
Ramon Fried <rfried.dev@gmail.com>
-
Add instructions to build and boot from QSPI Flash Signed-off-by:
Mamta Shukla <mamta.shukla@leica-geosystems.com> Signed-off-by:
Thomas Haemmerle <thomas.haemmerle@leica-geosystems.com> Tested-by:
Adam Ford <aford173@gmail.com> Reviewed-by:
Fabio Estevam <festevam@denx.de>
-
- Jul 21, 2022
-
-
Fix diacritics in some instances of my name and change my e-mail address to kabel@kernel.org. Add corresponding .mailmap entries. Signed-off-by:
Marek Behún <kabel@kernel.org> Reviewed-by:
Stefan Roese <sr@denx.de>
-
A common external watchdog circuit is kept alive by triggering a short pulse on the reset pin. This patch adds support for this use case, while making the algorithm configurable in the devicetree. The "linux,wdt-gpio" driver being modified is based off the equivalent driver in the Linux kernel, which provides support for this algorithm. This patch brings parity to this driver, and is kept aligned with the functionality and devicetree configuration in the kernel. It should be noted that this adds a required property named 'hw_algo' to the devicetree binding, following suit with the kernel. I'm happy to make this backward-compatible if preferred. Signed-off-by:
Paul Doelle <paaull.git@gmail.com> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Add support for hardware watchdog timer for Amlogic SoCs. This driver has been heavily inspired by his Linux equivalent (meson_gxbb_wdt.c). Reviewed-by:
Jerome Brunet <jbrunet@baylibre.com> Reviewed-by:
Neil Armstrong <narmstrong@baylibre.com> Signed-off-by:
Philippe Boos <pboos@baylibre.com> Reviewed-by:
Stefan Roese <sr@denx.de>
-