On Wed, 10 Dec 2025 at 18:10, Mathieu Dubois-Briand <[email protected]> wrote: > > On Wed Dec 10, 2025 at 1:42 PM CET, Mathieu Dubois-Briand wrote: > > On Wed Dec 10, 2025 at 5:37 AM CET, Dmitry Baryshkov via > > lists.openembedded.org wrote: > >> Upgrade Mesa to the latest release. Drop VDPAU tracker (dropped > >> upstream). Add support for ethosu and rocket Gallium drivers. > >> > >> Signed-off-by: Dmitry Baryshkov <[email protected]> > >> --- > > > > Hi Dmitry, > > > > Thanks for your patches. > > > > It looks like the new version is not building correctly for armv5: > > > > ERROR: mesa-2_25.3.1-r0 do_compile: Execution of > > '/srv/pokybuild/yocto-worker/qemuarmv5/build/build/tmp/work/armv5e-poky-linux-gnueabi/mesa/25.3.1/temp/run.do_compile.92740' > > failed with exit code 1 > > ... > > | In file included from > > ../sources/mesa-25.3.1/src/virtio/venus-protocol/vn_protocol_driver_cs.h:11, > > | from > > ../sources/mesa-25.3.1/src/virtio/venus-protocol/vn_protocol_driver_types.h:11, > > | from > > ../sources/mesa-25.3.1/src/virtio/venus-protocol/vn_protocol_driver_handles.h:11, > > | from > > ../sources/mesa-25.3.1/src/virtio/venus-protocol/vn_protocol_driver_structs.h:11, > > | from > > ../sources/mesa-25.3.1/src/virtio/venus-protocol/vn_protocol_driver_transport.h:12, > > | from > > ../sources/mesa-25.3.1/src/virtio/vulkan/vn_ring.c:10: > > | ../sources/mesa-25.3.1/src/virtio/vulkan/vn_ring.c:18:1: error: static > > assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint" > > | 18 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == > > 4, > > | | ^~~~~~~~~~~~~ > > > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2673 > > > > Can you have a look at the issue? > > > > Thanks, > > Mathieu > > Just a quick follow-up: it looks like the issue does not come from the > update but probably from another commit in this series. I dropped just > the last commit and still got the error: > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2675
I've sent v3, fixing the error. Indeed the issue existed even before the update. We didn't have the driver enabled. -- With best wishes Dmitry
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#227493): https://lists.openembedded.org/g/openembedded-core/message/227493 Mute This Topic: https://lists.openembedded.org/mt/116707522/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
