staging/hauke/package/boot, branch v21.02.3

ath79: add support for Yuncore A930

2022-04-16T12:48:45Z

Specification: - QCA9533 (650 MHz), 64 or 128MB RAM, 16MB SPI NOR - 2x 10/100 Mbps Ethernet, with 802.3at PoE support (WAN) - 2T2R 802.11b/g/n 2.4GHz Flash instructions: If your device comes with generic QSDK based firmware, you can login over telnet (login: root, empty password, default IP: 192.168.188.253), issue first (important!) 'fw_setenv' command and then perform regular upgrade, using 'sysupgrade -n -F ...' (you can use 'wget' to download image to the device, SSH server is not available): fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000" sysupgrade -n -F openwrt-...-yuncore_...-squashfs-sysupgrade.bin In case your device runs firmware with YunCore custom GUI, you can use U-Boot recovery mode: 1. Set a static IP 192.168.0.141/24 on PC and start TFTP server with 'tftp' image renamed to 'upgrade.bin' 2. Power the device with reset button pressed and release it after 5-7 seconds, recovery mode should start downloading image from server (unfortunately, there is no visible indication that recovery got enabled - in case of problems check TFTP server logs) Signed-off-by: Clemens Hopfer Signed-off-by: Thibaut VARÈNE (cherry-picked from commit a05dcb07241aa83a4416b56201e31b4af8518981) [switch to mtd-mac-address instead of nvmem-cells]

ath79: add support for Yuncore XD3200

2022-04-16T12:48:29Z

Specification: - QCA9563 (775MHz), 128MB RAM, 16MB SPI NOR - 2T2R 802.11b/g/n 2.4GHz - 2T2R 802.11n/ac 5GHz - 2x 10/100/1000 Mbps Ethernet, with 802.3at PoE support (WAN port) LED for 5 GHz WLAN is currently not supported as it is connected directly to the QCA9882 radio chip. Flash instructions: If your device comes with generic QSDK based firmware, you can login over telnet (login: root, empty password, default IP: 192.168.188.253), issue first (important!) 'fw_setenv' command and then perform regular upgrade, using 'sysupgrade -n -F ...' (you can use 'wget' to download image to the device, SSH server is not available): fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000" sysupgrade -n -F openwrt-...-yuncore_...-squashfs-sysupgrade.bin In case your device runs firmware with YunCore custom GUI, you can use U-Boot recovery mode: 1. Set a static IP 192.168.0.141/24 on PC and start TFTP server with 'tftp' image renamed to 'upgrade.bin' 2. Power the device with reset button pressed and release it after 5-7 seconds, recovery mode should start downloading image from server (unfortunately, there is no visible indication that recovery got enabled - in case of problems check TFTP server logs) Signed-off-by: Thibaut VARÈNE (cherry-picked from commit c91df224f54fdd44c9c0487a8c91876f5d273164)

uboot-bcm4908: use "xxd" from staging_dir

2022-03-15T17:55:08Z

This fixes: bash: xxd: command not found on hosts without xxd installed. Signed-off-by: Rafał Miłecki (cherry picked from commit 9dbca6bf6e6e088afd18fb532ed9135c21aec1cc) Fixes: 45b3f2aa0f57 ("uboot-bcm4908: add package with BCM4908 U-Boot")

uboot-bcm4908: add package with BCM4908 U-Boot

2022-03-14T07:51:01Z

New BCM4908 devices come with U-Boot instead of CFE. Firmwares for such devices has to include U-Boot. Signed-off-by: Rafał Miłecki (cherry picked from commit 0d45e1ea96ef29649f080c54f99fb1c80482421b)

uboot-envtools: mvebu: update uci defaults for Turris Omnia

2022-03-02T12:29:32Z

From version 2021.09 U-Boot will fixup Turris Omnia's DTB before booting, separating U-Boot's environment into separate MTD partition "u-boot-env" [1]. Check if "u-boot-env" MTD partition exists and set the uci defaults accordingly. [1] https://lists.denx.de/pipermail/u-boot/2021-July/455017.html Signed-off-by: Marek Behún (cherry picked from commit 713be7543909b79fbbccdea297e306cb3d3adb0c)

arm-trusted-firmware-bcm63xx: add ATF for Broadcom devices

2022-01-03T13:28:13Z

Right now it includes bcm4908 variant only that is required by BCM4908 family devices with U-Boot. Signed-off-by: Rafał Miłecki (cherry picked from commit f18288e26715f8cdef6c6d62a196dfd4ade8265e)

uboot-lantiq: danube: fix hanging lzma kernel uncompression #2

2021-11-27T22:00:31Z

Follow up to commit c744798cad6a13436f2ba9dd3a280cb16d315c85. Managed to hit the very same issue again while playing with the NOR SPL builds. Signed-off-by: Mathias Kresin

uboot-lantiq: danube: fix hanging lzma kernel uncompression

2021-11-14T19:24:45Z

At least since gcc 7.3.0 (OpenWrt 18.06) lwr/lwl are used in the assembly of LzmaProps_Decode. While the decission made by the compiler looks perfect fine, it triggers some obscure hang on lantiq danube-s v1.5 with MX29LV640EB NOR flash chips. Only if the offset 1 is used, the hang can be observed. Using any other offset works fine: lwl s0,0(a1) - s0 == 0x6d000080 lwl s0,1(a1) - hangs lwl s0,2(a1) - s0 == 0x0080xxxx lwl s0,3(a1) - s0 == 0x80xxxxxx It isn't clear whether it is a limitation of the flash chip, the EBU or something else. Force 8bit reads to prevent gcc optimizing the read with lwr/lwl instructions. Signed-off-by: Mathias Kresin

uboot-lantiq: fix sha1.h header clash when system libmd installed

2021-10-02T15:41:59Z

Backport of u-boot commit "includes: move openssl headers to include/u-boot" https://github.com/u-boot/u-boot/commit/2b9912e6a7df7b1f60beb7942bd0e6fa5f9d0167 Fixes: FS#3955 Signed-off-by: Alan Swanson (cherry picked from commit 8db641049292035604f0e1fb788608fdea879eca)

uboot-layerscape: fix dtc compilation on host gcc 10

2021-08-28T13:48:08Z

Backport a patch from upstream U-Boot to fix the compile with host GCC 10. Signed-off-by: Hauke Mehrtens (cherry picked from commit 8d143784cb8fafccdbcdc0bd5d1aa47d3d676f70)