I used these guides for cross-compiling and testing Mesa:
* https://github.com/anholt/mesa/wiki/Building-Mesa-for-VC4
* https://github.com/anholt/mesa/wiki/Raspberry-Pi-cross-compile
For targeting 64-bit you need to change all instances of arm-linux-gnueabihf to aarch-linux-gnu, and :armhf to :arm64. I think the most annoying part is that prerequisites differ on Buster (x11proto-dri2-dev may no longer exist, some additional wayland development libraries required) compared to what's on the wiki. You get to figure that parts out as meson initially complains about missing packages.
Also, on the Pi 3B+ it was enough to specify -Dgallium-drivers=vc4 but some users on the forums found out the hard way that it now needs all of vc4,v3d,kmsro
Good idea. Have called out 6by9 in the EXT_buffer_storage thread on the Pi forums.
* https://github.com/anholt/mesa/wiki/Building-Mesa-for-VC4
* https://github.com/anholt/mesa/wiki/Raspberry-Pi-cross-compile
For targeting 64-bit you need to change all instances of arm-linux-gnueabihf to aarch-linux-gnu, and :armhf to :arm64. I think the most annoying part is that prerequisites differ on Buster (x11proto-dri2-dev may no longer exist, some additional wayland development libraries required) compared to what's on the wiki. You get to figure that parts out as meson initially complains about missing packages.
Also, on the Pi 3B+ it was enough to specify -Dgallium-drivers=vc4 but some users on the forums found out the hard way that it now needs all of vc4,v3d,kmsro
(08-26-2019, 06:42 AM)bomblord Wrote: Might be worth getting that pi engineers input for a possible solution.
Good idea. Have called out 6by9 in the EXT_buffer_storage thread on the Pi forums.
