Add uImage.FIT partition parser and wire it up to allow mounting
filesystem sub-images from uImage.FIT in GPT partitions as well as
mtdblock and ubiblock devices within Linux (e.g. as root filesystem).
Using uImage.FIT to store the root filesystem besides kernel and dtb has
several obvious advantages which are hard to obtain in any other way:
* single image accross different storage types
* dynamically sized partitions for kernel and rootfs
* hash also for rootfs checked by U-Boot before launching kernel
* images may include additional filesystems e.g. for localization or
branding
For this to work, the image has to be created with external data and
sub-images aligned to the system's memory page boundaries, ie.
mkimage -E -B 0x1000 -p 0x1000 ...
Booting such images has been supported by U-Boot since v2018.01.
A previous version of this partition parser is in production use on some
OpenWrt devices, eg. the BananaPi R64 where using the FIT parser allows
booting the very same image from eMMC, SD Card or SPI-NAND/UBI and also
using it as a firmware-upgrade image at the same time.
The Ubiquiti UniFi 6 LR access point served as a reference board with
SPI-NOR flash and use of the partition parser on top of a mtdblock
device.
As U-Boot by now also passes down the selected configuration node name
via device tree this allows the partition parser (or userspace process
via sysfs) to identify the selected image configuration.
Device Tree schema for that:
https://github.com/devicetree-org/dt-schema/commit/a24d97d43491e55d4def006213213a6c4045b646
In most cases this partition parser can be used without relying on the
bootloader to pass-down the configuration node name. The default
configuration node is used then.
Changes since v3:
* use min_t(size_t, ...) when comparing sizes
* start enumerating uImage.FIT sub-images inside EFI/GPT partition
from p65
Changes since v2:
* use returned length to limit all strings read from fit/dt
* use __be32 type for 32-bit values read from fit/dt
Reported-by: kernel test robot <[email protected]>
* Kconfig: select LIBFDT for FIT_PARTITION
Reported-by: kernel test robot <[email protected]>
Changes since v1:
* Use again #ifdef's in partitions/efi to only build against FIT
parser symbols if it is actually selected. Otherwise the efi/gpt
would unconditionally depend on the FTT parser to be present.
Changes since RFC:
* fixed wrong variable used in error path
* introduced dedicated Kconfig options to enable partition
parsers on mtdblock and ubiblock
* drop #ifdef'ery, use IS_ENABLED(...) where needed
Daniel Golle (5):
block: add new flag to add partitions read-only
block: add partition parser for U-Boot uImage.FIT
partitions/efi: add support for uImage.FIT sub-partitions
mtd_blkdevs: add option to enable scanning for partitions
mtd: ubi: block: add option to enable scanning for partitions
MAINTAINERS | 6 +
block/blk.h | 1 +
block/partitions/Kconfig | 15 ++
block/partitions/Makefile | 1 +
block/partitions/check.h | 4 +
block/partitions/core.c | 6 +
block/partitions/efi.c | 9 +
block/partitions/efi.h | 3 +
block/partitions/fit.c | 353 ++++++++++++++++++++++++++++++++++++++
drivers/mtd/Kconfig | 11 ++
drivers/mtd/mtd_blkdevs.c | 4 +-
drivers/mtd/ubi/Kconfig | 10 ++
drivers/mtd/ubi/block.c | 5 +-
13 files changed, 426 insertions(+), 2 deletions(-)
create mode 100644 block/partitions/fit.c
--
2.38.1