- Jul 05, 2023
-
-
Compiling on armv7 results in: tools/renesas_spkgimage.c: In function ‘spkgimage_parse_config_line’: tools/renesas_spkgimage.c:76:66: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 3 has type ‘size_t’ {aka ‘unsigned int’} [-Wformat=] 76 | "config error: unknown keyword on line %ld\n", | ~~^ | | | long int | %d 77 | line_num); | ~~~~~~~~ | | | size_t {aka unsigned int} The correct printf specifier for size_t is '%zu'. Fixes: afdfcb11 ("tools: spkgimage: add Renesas SPKG format") Signed-off-by:Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
For changing the USB OTG node status from "okay" to "disabled" more space is needed, so call fdt_increase_size() to avoid the following error: ``` U-Boot 2023.07-rc5-0.0.0-devel+git.580eb311 (Jun 27 2023 - 13:39:58 +0000) CPU: Freescale i.MX7S rev1.2 800 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C) at 30C Reset cause: POR DRAM: initcall sequence 8786eafc failed at call 8781b351 (err=-3) ### ERROR ### Please RESET the board ### ``` Ideally, fdt_status_disabled() should call fdt_increase_size() internally, so that there would be no need for manually calling it in board code. Do it manually for now to fix the regression. Based on the code from board/CZ.NIC/turris_omnia/turris_omnia.c. Reported-by:
Francesco Dolcini <francesco.dolcini@toradex.com> Signed-off-by:
Fabio Estevam <festevam@denx.de> Reviewed-by:
-
add my patchwork alias Signed-off-by:Eugen Hristev <eugen.hristev@collabora.com>
-
- Jul 03, 2023
-
-
Tom Rini authored
Signed-off-by:Tom Rini <trini@konsulko.com>
-
Currently, spl_end points to the __bss_end address, which is an external RAM address instead of the end of the SPL text section in the internal RAM. This causes boot failures on imx6-colibri, for example: ``` Trying to boot from MMC1 SPL: Image overlaps SPL resetting ... ``` Fix this problem by assigning spl_end to _image_binary_end, as this symbol properly represents the end of the SPL text section. From u-boot-spl.map: .end *(.__end) 0x00000000009121a4 _image_binary_end = . Fixes: 77aed22b ("spl: spl_legacy: Add extra address checks") Reported-by:Marek Vasut <marex@denx.de> Tested-by: Marek Vasut <marex@denx.de> # DH i.MX6Q DHCOM PDK2
-
Pass _image_binary_end to make a standard way to indicate the end of the text section in SPL. The motivation for this is to have a uniform way to handle the SPL boundary checks. Signed-off-by:
-
Pass _image_binary_end to make a standard way to indicate the end of the text section in SPL. The motivation for this is to have a uniform way to handle the SPL boundary checks. Signed-off-by:
-
Fix two occurrences where 'signing' is misspelled. Signed-off-by:
Tim Harvey <tharvey@gateworks.com>
-
Use of CONFIG_SPL_FIT_SIGNATURE=y cause CONFIG_LEGACY_IMAGE_FORMAT=n as default, this prevent boot scripts in legacy image format from working and was an unintended change in the listed fixes commits: Wrong image format for "source" command Add CONFIG_LEGACY_IMAGE_FORMAT=y to defconfig for affected boards to restore support for boot scripts in legacy image format. Fixes: 3bf8e408 ("board: rockchip: add Radxa ROCK5B Rk3588 board") Fixes: cf777572 ("rockchip: rockpro64: Use SDMA to boost eMMC performance") Fixes: 6e2b8344 ("rockchip: rock-pi-4: Use SDMA to boost eMMC performance") Fixes: 1bf49d5a ("rockchip: rk3566-radxa-cm3-io: Update defconfig") Fixes: 703c170b ("rockchip: rk3568-evb: Update defconfig") Fixes: 68000f75 ("rockchip: rk3568-rock-3a: Update defconfig") Fixes: 6fb02589 ("rockchip: rk3588-evb: Update defconfig") Signed-off-by:
Jonas Karlman <jonas@kwiboo.se>
-
- Jul 01, 2023
-
-
https://source.denx.de/u-boot/custodians/u-boot-efiTom Rini authored
Pull request efi-2023-07-rc6 Documentation: * man-pages for the loads and saves commands UEFI: * fix implementation of allow_unaligned() for armv7 and arm11
-
Rename current assembler implementation of allow_unaligned() to arm11_arch_cp15_allow_unaligned() and add it into arm11.h header, then add C wrapper of allow_unaligned(). This fixes misbehavior when linking U-Boot, where the CPU specific allow_unaligned() implementation was ignored and instead the __weak allow_unaligned() implementation from lib/efi_loader/efi_setup.c was used, which led to "data abort" just before booting Linux via tftp, in efi_dp_from_file() -> path_to_uefi() -> utf16_put() . The problem is triggerd by c7c0ca37 ("efi_loader: fix efi_dp_from_file()") . Adding the wrapper fixes the problem. Fixes: d47a7746 ("arm: arm11: allow unaligned memory access") Signed-off-by:
-
Rename current assembler implementation of allow_unaligned() to v7_arch_cp15_allow_unaligned() and add it into armv7.h header, then add C wrapper of allow_unaligned(). This fixes misbehavior when linking U-Boot on ARMv7a i.MX6Q, where the CPU specific allow_unaligned() implementation was ignored and instead the __weak allow_unaligned() implementation from lib/efi_loader/efi_setup.c was used, which led to "data abort" just before booting Linux via tftp, in efi_dp_from_file() -> path_to_uefi() -> utf16_put() . The problem is triggerd by c7c0ca37 ("efi_loader: fix efi_dp_from_file()") . Adding the wrapper fixes the problem. Fixes: 78f90aae ("arm: armv7: allow unaligned memory access") Signed-off-by:
-
Heinrich Schuchardt authored
%s/loady/loadb/ Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Heinrich Schuchardt authored
Provide a man-page for the saves command. Signed-off-by:
-
Heinrich Schuchardt authored
Provide a man-page for the loads command. Signed-off-by:
-
- Jun 29, 2023
-
-
board_mmc_get_env_part() is not called as the default implementation of mmc_get_env_part() is used. Fix this problem by directly calling mmc_get_env_part() instead. Signed-off-by:
Eduard Strehlau <eduard@lionizers.com> Signed-off-by:
-
Tom Rini authored
Currently the PowerPC build job in Azure will hit the maximum time limit for a build and stop. Looking at the job, the easiest path to reducing it is to move Keymile vendor boards to their own job and exclude them from the PowerPC one (and while at this, the ls102 job). Signed-off-by:
Heiko Schocher <hs@denx.de>
-
Currently, the imx93_evk is configured with CONFIG_ENV_IS_IN_MMC and the chosen environment offset in the config is 0x400000. Unless the user programs the associated fuses, this offset is the default secondary boot image offset used by the i.MX 93 ROM bootloader. With certain combinations of environmental variables, the CRC and beginning of the environment can potentially falsely appear as a valid boot image container header. If the expected "sw_version" offset within this mistaken boot image container is greater than the primary's, the ROM bootloader can skip booting of the primary image altogether and attempt to boot with the content of the environment data. This will then hang the system. To fix this, move the environment from 0x400000 to 0x700000 reserving up to 3 MB at 0x400000 for any actual secondary user image container. Signed-off-by:
Ken Sloat <ken.s@variscite.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
-
https://source.denx.de/u-boot/custodians/u-boot-rockchipTom Rini authored
- rockchip inno phy fix; - pinctrl driver in SPL arort in specific case; - fix IO port voltage for rock5b-rk3588 board;
-
Update description with correct specifications Fixes: 3bf8e408 ("board: rockchip: add Radxa ROCK5B Rk3588 board") Signed-off-by:
Kever Yang <kever.yang@rock-chips.com>
-
Using CONFIG_ARMV8_SPL_EXCEPTION_VECTORS=y and CONFIG_OF_LIVE=y triggers a Data Abort exception from unaligned memory access when the pinctrl driver iterate node properties, e.g. for UART2 on RK3568. setting mux of GPIO0-24 to 1 setting mux of GPIO0-24 to 1 "Synchronous Abort" handler, esr 0x96000021 elr: 000000000000e554 lr : 000000000000e54c x 0: 0000000000000a5c x 1: 0000000000000a5c x 2: 0000000000000007 x 3: 0000000000000065 x 4: 0000000000000007 x 5: 0000000000022d4e x 6: 0000000000000a7c x 7: 00000000000227a4 x 8: 0000000000021cf0 x 9: 0000000000000a7c x10: 0000000000021cf0 x11: 0000000000021cf0 x12: 00000000003fda1c x13: 0000000000000007 x14: 00000000003fd9ec x15: 000000000001c0ff x16: 0000000007000000 x17: 00000000fdccd028 x18: 00000000003fde20 x19: 0000000000000018 x20: 0000000000020670 x21: 0000000000000000 x22: 00000000003fdb00 x23: 00000000003fef90 x24: 0000000000020688 x25: 0000000000000000 x26: 0000000000000001 x27: 00000000003ffc50 x28: 0000000000000000 x29: 00000000003fda60 Code: b94083e1 97ffd508 93407c01 37f81260 (f9401038) Resetting CPU ... Fix this by replacing the loop to access node properties with use of ofnode_for_each_prop instead of the current ifdef. Also continue to next prop instead of aborting at first sign of an unknown property. This fixes the Data Abort exception and also pinconf of e.g. pull and drive in SPL, e.g. for UART2 on RK3568. setting mux of GPIO0-24 to 1 setting mux of GPIO0-24 to 1 setting pull of GPIO0-24 to 5 setting mux of GPIO0-25 to 1 setting mux of GPIO0-25 to 1 setting pull of GPIO0-25 to 5 Fixes: e7ae4cf2 ("pinctrl: rockchip: Add common rockchip pinctrl driver") Signed-off-by:
-
This fixes access to camera sensor over I2C during probe time in the kernel. (Kernel will fix I/0 port voltage by itself, but the timing depends on probe order of the drivers, so the fix can come after the camera sensor driver already failed to probe.) Signed-off-by:
Ondrej Jirman <megi@xff.cz> Cc: Kever Yang <kever.yang@rock-chips.com> Reviewed-by:
Peter Robinson <pbrobinson@gmail.com> Tested-by:
-
The support for #address-cells=2 has a loophole: if the reg is actually 0, but the #address-cells is actually 1, like in such case below: syscon { #address-cells = <1>; phy { reg = <0 0x10>; }; }; then the second u32 of the 'reg' is the size, not the address. The code should check for the parent's #address-cells value, and not assume that if the first u32 is 0, then the #address-cells is 2, and the reg property is something like reg = <0 0xff00 0x10>; Fixed this by looking for the #address-cells value and retrieving the reg address only if this is ==2. To avoid breaking anything I also kept the check `if reg==0` as some DT's may have a wrong #address-cells as parent and even if this commit is correct, it might break the existing wrong device-trees. Fixes: d538efb9 ("phy: rockchip: inno-usb2: Add support #address_cells = 2") Signed-off-by:
-
- Jun 27, 2023
-
-
-
Bin Meng authored
In current linker script both .efi_runtime_rel and .rela.dyn sections are of RELA type whose entry size is either 12 (RV32) or 24 (RV64). These two are arranged as a continuous region on purpose so that the prelink-riscv executable can fix up the PIE addresses in one loop. However there is an 'ALIGN(8)' between these 2 sections which might cause a gap to be inserted between these 2 sections to satisfy the alignment requirement on RV32. This would break the assumption of the prelink process and generate an unbootable image. Fixes: 9a6569a0 ("riscv: Update alignment for some sections in linker scripts") Signed-off-by:
Bin Meng <bmeng@tinylab.org> Reviewed-by:
Rick Chen <rick@andestech.com>
-
Heinrich Schuchardt authored
Email account pragnesh.patel@sifive.com does not exist anymore. Signed-off-by: -
Yanhong Wang authored
Fixed errors reported when executing 'scripts/get_maintainer.pl -f configs/starfive_visionfive2_defconfig'. Invalid MAINTAINERS address: 'startfive' Signed-off-by:
Yanhong Wang <yanhong.wang@starfivetech.com> Reviewed-by:
Leo Yu-Chi Liang <ycliang@andestech.com>
-
- Jun 26, 2023
-
-
Tom Rini authored
Signed-off-by: -
Tom Rini authored
Rsync all defconfig files using moveconfig.py Signed-off-by: -
Two conflicting bootcmds were included in the environment. Streamline to defining the bootcmd only in the env file. Signed-off-by:
-
- Jun 25, 2023
-
-
Tom Rini authored
- Merge in a few important fixes. This includes a (partial) regression fix, updating documentation and some sanity checking around image loading.
-
- Jun 24, 2023
-
-
The current mechanism is unnecessarily complex. Simplify the whole mechanism such that the entire fitImage is signed, IVT is placed at the end, followed by CSF, and this entire bundle is also authenticated. This makes the signing scripting far simpler. Signed-off-by: -
In case the DEBUG is enabled, these three lines warn about cast of pointer to integer of different size, add the missing casts to fix the warnings. Signed-off-by: -
Check whether the loaded image or entry point does not overlap SPL. Signed-off-by: -
Add weak default reset_cpu() implementation needed by e.g. panic(). Signed-off-by: -
To avoid SRAM overflow in the SPL build, use simple malloc implementation. Signed-off-by: -
This removes dependency on fprintf() , which is not available in SPL unless full printf support is enabled. Signed-off-by:
-
- Jun 23, 2023
-
-
Fixed when build xilinx_zynqmp in long directory ( >256): | /buildarea1/testtest/wr_build/wr1023test_secureboot/test1-what/test2-what/test3-what/test4-what/test5-what/test6-what/test7-what/test8-what/test9-what/test10-what/test11-what/test12-what/build/tmp-glibc/work/xilinx_zynqmp-wrs-linux/u-boot-xlnx/1_v2023.01-xilinx-v2023.1+gitAUTOINC+40a08d69e7-r0/build/fitImage-linux: Image file name (uboot-mkimage) too long, can't create tmpfile. | Error: Bad parameters for FIT image type Signed-off-by:Mingli Yu <mingli.yu@windriver.com>
-
Tom Rini authored
With some changes to our mapping files in gitdm, re-generate the last few releases worth of statistics to correctly reflect contributions. We only go back this far to try and find a balance between highlighting contributions and still being reviewable. Signed-off-by: -
The intent here was to allow ANSI codes to be disabled, since it was proving impoosible to test operation of the menu code when it kept moving the cursor. Unfortunately this ended up in the patch. Correct this by enabling ANSI again. Signed-off-by:
Pali Rohár <pali@kernel.org> Reported-by:
Mark Kettenis <mark.kettenis@xs4all.nl> Reported-by:
Frank Wunderlich <frank-w@public-files.de> Fixes: 32bab0ea ("menu: Make use of CLI character processing") Tested-by:
Mark Kettenis <kettenis@openbsd.org> Reviewed-by:
-
