- 26 3月, 2020 2 次提交
-
-
由 Kever Yang 提交于
Use syscon API to get grf base instead of get from dts. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Kever Yang 提交于
Use syscon API to get grf base instead of get from dts. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Acked-by: NOtavio Salvador <otavio@ossystems.com.br>
-
- 23 3月, 2020 2 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-efi由 Tom Rini 提交于
Pull request for UEFI sub-system for efi-2020-04-rc4 (5) This series contains bug fixes for the UEFI sub-system: * report correct variable length in GetNextVariable() * correct copying direction if freestanding memmove() * remove const for parameter of GetNextVariableName() * correct function descriptions Unit tests are added and adjusted.
-
由 Heinrich Schuchardt 提交于
'vendor' is both an input and an output parameter. So it cannot be constant. Fixes: 0bda81bf ("efi_loader: use const efi_guid_t * for variable services") Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 22 3月, 2020 8 次提交
-
-
由 Heinrich Schuchardt 提交于
Provide unit tests for CalculateCrc32(), CopyMem(), SetMem(). Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
For EFI binaries we have to provide an implementation of memmove() in efi_freestanding.c. Before this patch the memmove() function was copying in the wrong direction. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Correct the description of function efi_convert_pointer(). Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
To check if a variable is non-zero there is no need for '!= 0'. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
GetNextVariableName should report the length of the variable including the final 0x0000 in bytes. Check this in the unit test. Increase the buffer size for variable names. 40 bytes is too short. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
The runtime service GetNextVariable() returns the length of the next variable including the closing 0x0000. This length should be in bytes. Comparing the output of EDK2 and U-Boot shows that this is currently not correctly implemented: EDK2: OsIndicationsSupported: 46 PlatformLang: 26 PlatformLangCodes: 36 U-Boot: OsIndicationsSupported: 23 PlatformLang: 13 PlatformLangCodes: 18 Provide correct length in GetNextVariable(). Fixes: d99a87f8 ("efi_loader: implement GetNextVariableName()") Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Use Sphinx style for function descriptions. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Correct the file description. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 18 3月, 2020 4 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-sunxi由 Tom Rini 提交于
- Revert "sunxi: psci: avoid error address-of-packed-member"
-
https://gitlab.denx.de/u-boot/custodians/u-boot-efi由 Tom Rini 提交于
Pull request for UEFI sub-system for efi-2020-04-rc4 (4) This series fixes several bugs: * consider the /reserved-memory node in the device tree * consider memory reservations created in ft_board_setup() * correct output of 'efidebug memmap' on the sandbox * correct the definition of efi_capsule_header() Furthermore some definitions needed for future patches are added to header files.
-
https://gitlab.denx.de/u-boot/custodians/u-boot-riscv由 Tom Rini 提交于
- Fix sbi_remote_sfence_vma{,_asid}. - Avoid calling sbi_clear_ipi(). - Add new SBI v0.2 extensions support.
-
由 Tomasz Duszynski 提交于
Using memcpy() for some MMIO access is generally frowned upon and might break things on some platforms. Allwinner H3, which fails to boot, being an example here. Moreover, fields being accessed are naturally aligned and warnings produced by GCC have been quiesced for some time already by: 53dc8ae6 ("gcc-9: silence 'address-of-packed-member' warning") That said, it should be okay to revert this commit. This reverts commit 9bd34a69. Cc: Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: NTomasz Duszynski <tduszyns@gmail.com> Acked-by: NJagan Teki <jagan@amarulasolutions.com>
-
- 17 3月, 2020 15 次提交
-
-
由 AKASHI Takahiro 提交于
See UEFI specification, section 8.5.3. In addition, the structure, efi_capsule_header, should be "packed" as it is a serialized binary format in a capsule file. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>
-
由 AKASHI Takahiro 提交于
This is a preparatory patch. Those functions will be used in an implementation of UEFI firmware management protocol as part of my capsule update patch. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>
-
由 AKASHI Takahiro 提交于
Some of those values will be used in an implementation of UEFI firmware management protocol as part of my capsule update patch. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>
-
由 AKASHI Takahiro 提交于
These flags are expected to be set in OsIndicationsSupported variable if corresponding features are supported. See UEFI specification, section 8.5.4. In particular, capsule-related flags will be used in my capsule update patch. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org> Fix misspelled EFI_OS_INDICATIONS_BOOT_TO_FW_UI. Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Atish Patra 提交于
Currently, bootefi only parses memory reservation block to setup EFI reserved memory mappings. However, it doesn't parse the reserved-memory[1] device tree node that also can contain the reserved memory regions. Add capability to parse reserved-memory node and update the EFI memory mappings accordingly. 1. <U-Boot source>/doc/device-tree-bindings/reserved-memory/reserved-memory.txt] Signed-off-by: NAtish Patra <atish.patra@wdc.com> Fix an endless loop. The /reserved-memory node may have children without reg property. Remove a superfluous debug statement. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Addresses in the sandbox's device tree are in the sandbox's virtual address space. If we want to compare memory reservations in the device-tree with the output of 'efidebug memmap', we need to convert back to this address space. Adjust the output of the 'efidebug memmap' command. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Some memory reservations are made in ft_board_setup(). Ensure that we create reserved memory map entries after ft_board_setup(). The downside of this patch is that if bootefi is called multiple times with an devicetree argument superfluous reservations for the old copies of the device tree will exist. But that is still better than missing a reservation. Deleting the superfluous reservations is not possible because reservations in the memory map are rounded to page size and may be coallesced. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Bin Meng 提交于
Few v0.1 SBI calls are being replaced by new SBI calls that follows v0.2 calling convention. Implement the replacement extensions and few additional new SBI function calls that makes way for a better SBI interface in future. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NPragnesh Patel <pragnesh.patel@sifive.com>
-
由 Bin Meng 提交于
We now have SBI v0.2 which is more scalable and extendable to handle future needs for RISC-V supervisor interfaces. Introduce a new config and move all SBI v0.1 code under that config. This allows to implement the new replacement SBI extensions cleanly and remove v0.1 extensions easily in future. Currently, the config is enabled by default. Once all M-mode software, with v0.1, is no longer in use, this config option and all relevant code can be easily removed. This commit is inspired from Linux kernel patch: https://patchwork.kernel.org/patch/11407361/Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NPragnesh Patel <pragnesh.patel@sifive.com>
-
由 Bin Meng 提交于
Few v0.1 SBI calls are being replaced by new SBI calls that follows v0.2 calling convention. This patch just defines these new extensions. This commit is inspired from Linux kernel patch: https://patchwork.kernel.org/patch/11407359/Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NPragnesh Patel <pragnesh.patel@sifive.com>
-
由 Bin Meng 提交于
The SBI v0.2 introduces a base extension which is backward compatible with v0.1. Implement all helper functions and minimum required SBI calls from v0.2 for now. All other base extension function will be added later as per need. As v0.2 calling convention is backward compatible with v0.1, remove the v0.1 helper functions and just use v0.2 calling convention. Add a new Kconfig options CONFIG_SBI for the new SBI v0.2 codes, and let CONFIG_SBI_IPI depend on it. This commit is inspired from Linux kernel patch: https://patchwork.kernel.org/patch/11407363/Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NPragnesh Patel <pragnesh.patel@sifive.com>
-
由 Bin Meng 提交于
As per the new SBI specification, current SBI implementation version is defined as 0.1 and will be removed/replaced in future. Each of the function call in 0.1 is defined as a separate extension which makes easier to replace them one at a time. Rename existing implementation to reflect that. This patch is just a preparatory patch for SBI v0.2 and doesn't introduce any functional changes. This commit is inspired from Linux kernel patch: https://patchwork.kernel.org/patch/11407355/Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NPragnesh Patel <pragnesh.patel@sifive.com>
-
由 Bin Meng 提交于
There is no need for S-mode U-Boot to call sbi_clear_ipi() as it can be cleared directly from S-mode. This saves some cycles. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NLukas Auer <lukas@auer.io>
-
由 Bin Meng 提交于
Currently sbi_remote_sfence_vma{,_asid} does not pass their arguments to SBI at all, which is semantically incorrect. This keeps in sync with Linux kernel commit: a21344dfc6ad: fix sbi_remote_sfence_vma{,_asid} Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NLukas Auer <lukas@auer.io>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-marvell由 Tom Rini 提交于
- Fix timer wrap (Chris) - Use dev_read only if OF_PLATDATA is not enabled (Walter)
-
- 16 3月, 2020 2 次提交
-
-
由 Chris Packham 提交于
On some platforms/architectures the value from get_timer() can wrap. This is particularly problematic when long-running code needs to measure a time difference as is the case with watchdog_reset() which tries to avoid tickling the watchdog too frequently. Use time_after() from time.h instead of a plain > comparison to avoid any issues with the time wrapping on a system that has been sitting in u-boot for a long time. Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NStefan Roese <sr@denx.de>
-
由 Walter Lozano 提交于
Currently watchdog tries to use dev_read_u32_default to get timeout configuration in case OF_CONTROL is enabled. However, if SPL is built with OF_PLATDATA this has no sense as there is no device tree. This patch fixes this issue by only use dev_read_u32_default if OF_CONTROL is enabled but OF_PLATDATA is not. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
- 14 3月, 2020 1 次提交
-
-
由 Tom Rini 提交于
- Address the regression with the 'gpio' command - Fix mcfuart regression - Other minor fixes
-
- 13 3月, 2020 6 次提交
-
-
由 Patrice Chotard 提交于
Add STi drivers/include files and git tree. Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Heinrich Schuchardt 提交于
GCC-10 reports: In file included from tools/common/image-fit.c:1: include/image.h: In function ‘fit_image_get_data_and_size’: ./tools/../common/image-fit.c:1015:9: warning: ‘len’ may be used uninitialized in this function [-Wmaybe-uninitialized] 1015 | *size = len; | ~~~~~~^~~~~ ./tools/../common/image-fit.c:996:6: note: ‘len’ was declared here 996 | int len; | ^~~ Add the missing check of the return value of fit_image_get_data_size(). Fixes: c3c86388 ("add FIT data-position & data-offset property support") Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
-
由 Michal Simek 提交于
Just cleanup help indentation to be the same for all options. It means <tab><space><space> indentation. OMAP3 should be indented by tabs which is also fixed. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Alex Kiernan 提交于
4dbc107f ("cmd: gpio: Correct do_gpio() return value") correctly changed the behaviour of the gpio command to return CMD_RET_SUCCESS or CMD_RET_FAILURE, but any existing script which expects the return value to be the pin value is broken by this change. Reinstate the legacy behaviour for `gpio input` only. Fixes: 4dbc107f ("cmd: gpio: Correct do_gpio() return value") Signed-off-by: NAlex Kiernan <alex.kiernan@gmail.com> Signed-off-by: NAlex Kiernan <alex.kiernan@hivehome.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 AKASHI Takahiro 提交于
The commit 5fed97af ("Makefile: ensure DTB doesn't overflow into initial stack") adds an extra check for stack size in BSS if CONFIG_SYS_INIT_SP_BSS_OFFSET is enabled. This check, however, doesn't make sense under the configuration where control dtb won't be built in and it should be void in such cases. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org> Fixes: 5fed97af ("Makefile: ensure DTB doesn't overflow into initial stack") Reviewed-by: NStephen Warren <swarren@nvidia.com>
-
由 Angelo Durgehello 提交于
All drivers seems to align now to serial_xxx maning, so, aligning also this driver, to allow to be found easily. Signed-off-by: NAngelo Durgehello <angelo.dureghello@timesys.com>
-