Also look at the meta-xil...@lists.yoctoproject.org, they should be able
to answer petalinux questions and how to migrate off petalinux.
Philip
On 7/10/24 17:18, Alexander Kanavin wrote:
I suspect with plain Yocto, you're simply going to have one build for
everything and an image that boots everywhere, with MACHINE set to
zynqmp_generic. You need to try and see.
Alex
On Wed, 10 Jul 2024 at 15:28, philip.dawson via Lists.Yoctoproject.Org
<philip.dawson=datapath.co...@lists.yoctoproject.org> wrote:
OK, thank you for your help. I'll ask on the Xilinx forums.
Out of interest if I was to work to extract ourselves from Petalinux, do you have any
brief idea how you might go about supporting 4 device trees -> 1 kernel if this
was a pure Yocto build? Or if that's not sensible how to break the kernel driver
header -> user-space dependency that's causing us to have to recompile our
software?
Best Regards,
Phil
On Wed, Jul 10, 2024 at 02:19 PM, Alexander Kanavin wrote:
If you're using petalinux, then you should ask for support from the
petalinux provider.
On the other hand it's probably possible to transition to a direct
yocto build using only standard yocto upstream mechanisms, without all
the extra custom BSP generation, and then you'd be better able to
control how the build gets constructed, and to get help with that in
this forum.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63464): https://lists.yoctoproject.org/g/yocto/message/63464
Mute This Topic: https://lists.yoctoproject.org/mt/107140139/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
