fix-qemu-ppce500-with-binutils-2.38
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
Gbp-Pq: Name fix-qemu-ppce500-with-binutils-2.38.patch
rockchip-inno-usb
Downloaded from:
https://patchwork.ozlabs.org/project/uboot/patch/
20210406151059.
1187379-1-icenowy@aosc.io
Downloaded from:
https://patchwork.ozlabs.org/project/uboot/patch/
20210406151059.
1187379-1-icenowy@aosc.io
From: Icenowy Zheng <icenowy@aosc.io>
To: Simon Glass <sjg@chromium.org>, Kever Yang <kever.yang@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>,
Jagan Teki <jagan@amarulasolutions.com>
Cc: u-boot@lists.denx.de,
Icenowy Zheng <icenowy@aosc.io>
Subject: [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>
Gbp-Pq: Topic rockchip
Gbp-Pq: Name rockchip-inno-usb.patch
prevent relocating initrd & fdt, that results in failure to boot
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/
1937246
===================================================================
Gbp-Pq: Topic riscv64
Gbp-Pq: Name unmatched-prevent-relocating-initrd-and-fdt.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.
Bug-Debian: https://bugs.debian.org/920116
Signed-off-by: Benjamin Drung <bdrung@debian.org>
Gbp-Pq: Topic exynos
Gbp-Pq: Name 0001-arm-config-fix-default-console-only-to-specify-the-d.patch
u-boot (2023.01+dfsg-2) unstable; urgency=medium
* debian/patches: Apply patch submitted upstream fixing booting with
qemu-riscv64. (Closes: #
1028343)
[dgit import unpatched u-boot 2023.01+dfsg-2]
projects / u-boot.git / log