Status update. Got what I wanted KDE Plasma on gles2 running on wayland. Lots of driver memory errors and coredumps though.
WHY? My best guess is lima is not ready yet. I dont believe panfrost is the right driver. from what I read...why would there be a lima if pf worked. QT5 is not built for gles correctly on Arch-manjaro for sure and probly the same for all the other arm distro's.
Trying to make lots of boards work with a generic mesa-qt5 is not the way imo. This board needs a dev and/or user group to each setup with a arm64 compiler (a task all to itself) and get to building ROCK64 packages to get to it being usable for an acellerated compositor like kwin plus browser video accel.. Lots of env vars have to be experimented with and set too. I'm sure then..that work could be adapted to other boards fairly easily by changing lima for w/e driver that arm board uses. Same for cpu. Question is...which board will get this kind of group effort? I don't see the r64 getting it. I may have to get an RPI4 just so I have help to turn to. due to user base size.
So I launched into building a aarch64 cross compiler on x86_64 box laying around on Arch Linux. Hand built it with the latest pkgs too like gccv9.2 in /opt
from a tute at preshing.com. I'm in touch with an original LFS member on getting a new enbedded arm book together. Don't know him so we shall see. Said he's buying the rock64 board. So I'm set to do what I can by first building qt5 w/ gles and then kde plasma pkgs. Something I do alot on LFS x86-64 since it's my daily driver OS. Once you build from source with all the perks/options that brings ...I don't use distro's except for certain tasks like servers or arm compilers.
WHY? My best guess is lima is not ready yet. I dont believe panfrost is the right driver. from what I read...why would there be a lima if pf worked. QT5 is not built for gles correctly on Arch-manjaro for sure and probly the same for all the other arm distro's.
Trying to make lots of boards work with a generic mesa-qt5 is not the way imo. This board needs a dev and/or user group to each setup with a arm64 compiler (a task all to itself) and get to building ROCK64 packages to get to it being usable for an acellerated compositor like kwin plus browser video accel.. Lots of env vars have to be experimented with and set too. I'm sure then..that work could be adapted to other boards fairly easily by changing lima for w/e driver that arm board uses. Same for cpu. Question is...which board will get this kind of group effort? I don't see the r64 getting it. I may have to get an RPI4 just so I have help to turn to. due to user base size.
So I launched into building a aarch64 cross compiler on x86_64 box laying around on Arch Linux. Hand built it with the latest pkgs too like gccv9.2 in /opt
from a tute at preshing.com. I'm in touch with an original LFS member on getting a new enbedded arm book together. Don't know him so we shall see. Said he's buying the rock64 board. So I'm set to do what I can by first building qt5 w/ gles and then kde plasma pkgs. Something I do alot on LFS x86-64 since it's my daily driver OS. Once you build from source with all the perks/options that brings ...I don't use distro's except for certain tasks like servers or arm compilers.