Hey,

When we're building a full software setup for a certain embedded architecture 
to completly setup a device, that contains various components which are 
collected in some "post-rootfs-packaging"

* A rootfs
* Kernel
* Bootloaders
* Firmware
* potentially setup components not ending up on the final device state 
(initramfs for USB bootstrap for example)
* tooling for USB/flasher/etc (eg ADB)

Those to bootstrap a device (e.g. via USB/flasher/...), something therefore 
collects the output of various recipes, both images (rootfs) and non-images 
(bootloader files, firmware, ...) and packages them in a custom way. Often this 
includs additional tooling, like flashing tools or install scripting. Working 
with various SoC vendors, I've seen various setups, and I'm not sure if there 
is any guidance on whats correct

* Some vendors have external tooling. This tooling expects the right files in 
the right place (eg. deploy dir) to bootstrap a device
* Some vendors integrate this into yocto, having a custom recipe that depends 
on recipes and packages the output
* Some meta-layers for OTA update do something similar, inherit the image type, 
but disable most image tasks and don't actually build an "image" (e.g. swupdate)
* Some vendors implement custom image types

When trying to support multiple SoC/BSP vendors, this sometimes leads to 
conflicts and questions, but I was unable to find some references to this in 
the yocto documentation. A custom image type feels most integrated into yocto, 
but I've seen some "hacks" in there that make me question if this is intended? 
Is there anything like a reference implementation for "post-rootfs-packaging"?

Best regards, Olli
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64614): https://lists.yoctoproject.org/g/yocto/message/64614
Mute This Topic: https://lists.yoctoproject.org/mt/110768646/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to