]> code.ossystems Code Review - openembedded-core.git/commit
wic: allow multiple /boot partitions with different content
authorEnrico Scholz <enrico.scholz@ensc.de>
Fri, 8 Sep 2017 17:33:02 +0000 (19:33 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 22 Sep 2017 16:15:46 +0000 (17:15 +0100)
commit8c1dec627e9735260516fe8f0b2bfdb0ee70172b
tree834157081f1d28d187d8eb0b910a85b28c1ea986
parentacc5036a6b74a76d719e6f7224a398f47df4a041
wic: allow multiple /boot partitions with different content

It can be useful to have multiple partitions with '--source bootimg-partition'
but different content.

E.g. for TI AM335x, one boot partition can contain an first stage
bootloader ("MLO"), while the real bootloader and kernel plus devicetree
are in another one.

Patch allows to specify multiple IMAGE_BOOT_FILES with optional "_label-XXX"
or "_uuid-XXX" overrides.

E.g. with this patch, a .wks file with

| part --source bootimg-partition ... --label=mlo --active
| part --source bootimg-partition ... --label=boot0
| part --source bootimg-partition ... --label=boot1

and a recipe with

| IMAGE_BOOT_FILES_label-mlo = "\
|   MLO-${MACHINE}.img;MLO \
| "
|
| IMAGE_BOOT_FILES_label-boot0 = "\
|   u-boot-${MACHINE}.img;u-boot.img \
|   zImage \
| "
|
| IMAGE_BOOT_FILES_label-boot1 = "${IMAGE_BOOT_FILES_label-boot0}"
|
| WICVARS += " \
|   IMAGE_BOOT_FILES_label-mlo \
|   IMAGE_BOOT_FILES_label-boot0 \
|   IMAGE_BOOT_FILES_label-boot1 \
| "

is possible.  It will create one partition with the MLO and two redundant
ones with the uboot + kernel.

Signed-off-by: Enrico Scholz <enrico.scholz@ensc.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
scripts/lib/wic/plugins/source/bootimg-partition.py