configs/mx53loco_defconfig | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

---

Makefile | 3 3 + 0 - 0 !
1 file changed, 3 insertions(+)

 add spl/arndale-spl.bin rule

test/image/test-imagetools.sh | 26 13 + 13 - 0 !
1 file changed, 13 insertions(+), 13 deletions(-)

---

board/samsung/common/bootscripts/autoboot.cmd | 2 1 + 1 - 0 !
board/samsung/common/bootscripts/bootzimg.cmd | 4 2 + 2 - 0 !
board/samsung/common/dfu_sample_env.txt | 4 2 + 2 - 0 !
include/configs/odroid.h | 2 1 + 1 - 0 !
include/configs/odroid_xu3.h | 2 1 + 1 - 0 !
include/configs/s5p_goni.h | 2 1 + 1 - 0 !
include/configs/s5pc210_universal.h | 2 1 + 1 - 0 !
include/configs/trats.h | 2 1 + 1 - 0 !
include/configs/trats2.h | 2 1 + 1 - 0 !
9 files changed, 11 insertions(+), 11 deletions(-)

 [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.

Bug-Debian: https://bugs.debian.org/920116
Signed-off-by: Benjamin Drung <bdrung@debian.org>

include/configs/sifive-unmatched.h | 2 2 + 0 - 0 !
1 file changed, 2 insertions(+)

 prevent relocating initrd & fdt, that results in failure to boot

test/image/test-imagetools.sh | 12 0 + 12 - 0 !
1 file changed, 12 deletions(-)

---

drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 21 21 + 0 - 0 !
1 file changed, 21 insertions(+)

 [patch] phy: rockchip: inno-usb2: fix hang when multiple controllers
 exit
Date: Tue,  6 Apr 2021 23:10:59 +0800
Message-Id: <20210406151059.1187379-1-icenowy@aosc.io>

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.

Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Fixes: ac97a9ece14e ("phy: rockchip: Add Rockchip USB2PHY driver")
Tested-by: Peter Robinson <pbrobinson@gmail.com>

configs/roc-pc-mezzanine-rk3399_defconfig | 2 2 + 0 - 0 !
configs/roc-pc-rk3399_defconfig | 2 2 + 0 - 0 !
2 files changed, 4 insertions(+)

 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.

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

configs/qemu-x86_64_defconfig | 2 2 + 0 - 0 !
configs/qemu_arm64_defconfig | 2 2 + 0 - 0 !
2 files changed, 4 insertions(+)

 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

arch/powerpc/cpu/mpc85xx/tlb.c | 21 17 + 4 - 0 !
1 file changed, 17 insertions(+), 4 deletions(-)

---

Makefile | 8 6 + 2 - 0 !
1 file changed, 6 insertions(+), 2 deletions(-)

 [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/

Series-to: u-boot

Signed-off-by: Vagrant Cascadian <vagrant@reproducible-builds.org>

configs/tools-only_defconfig | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

---

boot/vbe_simple_os.c | 16 12 + 4 - 0 !
1 file changed, 12 insertions(+), 4 deletions(-)

 [patch v2] vbe: allow probing the vbe bootmeth to fail in os fixup
Date: Thu, 12 Jan 2023 16:48:54 -0700
Message-Id: <20230112234854.936325-1-sjg@chromium.org>

drivers/timer/orion-timer.c | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 [patch] timer: orion-timer: fix problem in early_init_done()
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

It was noticed that Clearfog is currently broken with this newly
introduced early_init_done() function. Apparently the timer is enabled
here when U-Boot is run but not configured - at least not correctly.
Resulting in a hangup in the timer reading functions.

To fix this, also read the value of the reload register and check it's
value with the one written to by U-Boot. Only if this matches, the
init has already been done.

Fixes: 5387b093cb79 ("timer: orion-timer: Fix problem with early static variable")
Signed-off-by: Stefan Roese <sr@denx.de>