Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
mx53loco | Enables support for ext4, the "load" command, and using bootz with raw initrds. | no | ||||
arndale/board-spl-rule.diff | Add spl/arndale-spl.bin rule =================================================================== |
Ian Campbell <ijc@debian.org> | no | |||
test-imagetools-test-fixes | This patch allows testing in an alternate directory and also detects failures to execute commands, treating that as a failure. |
no | ||||
qemu/efi-secure-boot.patch | enable support for secure boot on qemu arm64/amd64 Secure boot is now supported upstream in EFI mode. It is disabled by default, and can be enabled by loading keys from the console: https://u-boot.readthedocs.io/en/latest/develop/uefi/uefi.html#configuring-uefi-secure-boot |
Luca Boccassi <bluca@debian.org> | no | |||
fix-qemu-ppce500-with-binutils-2.38.patch | Fix building qemu-ppce500 target with binutils ~2.38. https://bugs.debian.org/1003490 The incompatibility was introduced in binutils commit: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a |
no | ||||
exynos/0001-arm-config-fix-default-console-only-to-specify-the-d.patch | [PATCH] arm: config: fix default console only to specify the device This reverts commit 767edf0f6b3eaa0303f3fd6afdc14ddce0aca70c and restores commit 232ed3ca534708527a9515c7c41bc3542949525c. Debian's flash-kernel expect the console variable to just contain the device, because it will set the bootargs to "console=${console}". So revert adding "console=" to the console parameter, but also adjust the shipped bootscripts for exynos boards to cope with it. |
Dongjin Kim <tobetter@gmail.com> | no | debian | 2017-10-28 | |
riscv64/unmatched-prevent-relocating-initrd-and-fdt.patch | prevent relocating initrd & fdt, that results in failure to boot=================================================================== | Heinrich Schuchardt (xypron) | no | |||
disable-fit-image-tests | Disable FIT image tests. FIT images were made more robust in light of CVE-2021-27097 and CVE-2021-27138, but test-imagetools.sh was not updated to reflect those changes. Reported upstream: https://lists.denx.de/pipermail/u-boot/2021-March/443460.html diff --git a/test/image/test-imagetools.sh b/test/image/test-imagetools.sh index 907f46a7b5..e3b341b9e9 100755 |
no | ||||
rockchip/rockchip-inno-usb.patch | [PATCH] phy: rockchip: inno-usb2: fix hang when multiple controllers exit The OHCI and EHCI controllers are both bound to the same PHY. They will both do init and power_on operations when the controller is brought up and both do power_off and exit when the controller is stopped. However, the PHY uclass of U-Boot is not as sane as we thought -- they won't maintain a status mark for PHYs, and thus the functions of the PHYs could be called for multiple times. Calling init/power_on for multiple times have no severe problems, however calling power_off/exit for multiple times have a problem -- the first exit call will stop the PHY clock, and power_off/exit calls after it still trying to write to PHY registers. The write operation to PHY registers will fail because clock is already stopped. Adapt the count mechanism from phy-sun4i-usb to both init/exit and power_on/power_off functions to phy-rockchip-inno-usb2 to fix this problem. With this stopping USB controllers (manually or before booting a kernel) will work. |
Icenowy Zheng <icenowy@aosc.io> | no | 2021-04-06 | ||
rockchip/rockchip-roc-pc-rk3399-Enable-rockchip-efuse-support.patch | configs: roc-pc-rk3399: Enable rockchip efuse support Enable efuse support which allows reading of the cpuid#, serial# and also generates a unique mac address from the board's serial. |
Christopher Obbard <chris.obbard@collabora.com> | yes | 2022-11-23 | ||
Makefile-Use-relative-paths-for-debugging-symbols.patch | [PATCH] Makefile: Use relative paths for debugging symbols. The KBUILD_CFLAGS and KBUILD_AFLAGS variables are adjusted to use -ffile-prefix-map and --debug-prefix-map, respectively, to use relative paths for occurrences of __FILE__ and debug paths. This enables reproducible builds regardless of the absolute path to the build directory: https://reproducible-builds.org/docs/build-path/ |
Vagrant Cascadian <vagrant@reproducible-builds.org> | no | 2022-08-16 | ||
tools-disable-video-logo | Disable video logo as this breaks cross-building, which runs bmp_logo during the build to generate the logo headers. Debian does not currently ship the bmp_logo tool, so simply disable this feature. =================================================================== |
no | ||||
riscv64/vbe-Allow-probing-the-VBE-bootmeth-to-fail-in-OS-fixup.patch | [PATCH v2] vbe: Allow probing the VBE bootmeth to fail in OS fixup This device is created when there are no bootmeths defined in the device tree. But it cannot be probed without a device tree node. For now, ignore a probe failure. |
Simon Glass <sjg@chromium.org> | no | debian | https://patchwork.ozlabs.org/project/uboot/patch/20230112234854.936325-1-sjg@chromium.org/ | 2023-01-12 |