openwrt/target
Rafał Miłecki 93259e8ca2 bcm4908: support "rootfs_data" on U-Boot devices
1. Create "rootfs_data" dynamicaly

U-Boot firmware images can contain only 2 UBI volumes: bootfs (container
with U-Boot + kernel + DTBs) and rootfs (e.g. squashfs). There is no way
to include "rootfs_data" UBI volume or make firmware file tell U-Boot to
create one.

For that reason "rootfs_data" needs to be created dynamically. Use
preinit script to handle that. Fire it right before "mount_root" one.

2. Relate "rootfs_data" to flashed firmware

As already explained flashing new firmware with U-Boot will do nothing
to the "rootfs_data". It could result in new firmware reusing old
"rootfs_data" overlay UBI volume and its file. Users expect a clean
state after flashing firmware (even if flashing the same one).

Solve that by reading flash counter of running firmware and storing it
in "rootfs_data" UBI volume. Every mismatch will result in wiping old
data.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
2022-03-04 16:14:59 +01:00
..
imagebuilder imagebuilder: fix local packages/ folder 2021-11-05 19:18:48 -10:00
linux bcm4908: support "rootfs_data" on U-Boot devices 2022-03-04 16:14:59 +01:00
llvm-bpf llvm-bpf: fix rebuild check for generating tarball 2021-11-26 11:37:19 +01:00
sdk build: scripts/config - update to kconfig-v5.14 2022-02-19 13:10:01 +01:00
toolchain toolchain: switch packaged toolchain to tar.xz 2021-10-21 08:25:38 -10:00
Config.in base-files: add eMMC sysupgrade support 2021-12-02 20:42:58 +00:00
Makefile tools/llvm-bpf: move tarball packing to target/llvm-bpf 2021-11-22 12:00:40 +01:00