These current builds are done using zynqmp-generic as the machine target, and
then external (petalinux specific) scripting that combines them with target
specific boot.bin & linux firmware for the image.
I'll let Varalaxmi comment, she's far more of an expert on what is happening in
PetaLinux then I am.
--Mark
On 7/11/24 9:27 AM, philip.dawson via lists.yoctoproject.org wrote:
Hi Varalaxmi,
Thank you for the link to the prebuilt rootfs images.
All our products are on a single SOC family (zynqmp).
We'd like to build our own custom common versions of Kernel/Rootfs (with our
patches and software) just once, and then use that as the basis for images for
our multiple products (each with different device trees, PL bitstreams &
bootloaders).
I can't work out if this is possible within yocto/petalinux tool flows - or if
we'd need to define a dummy/common project that builds the kernel and rootfs,
and then manually build only the bootloaders, devicetrees and FIT images for
each specific product.
I'm really caught up on the device-tree -> kernel dependency. It seems odd to
have to rebuild the kernel just because the device tree has changed. Am I
misunderstanding this?
Regards,
Phil
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5452):
https://lists.yoctoproject.org/g/meta-xilinx/message/5452
Mute This Topic: https://lists.yoctoproject.org/mt/107162406/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
