It’s unactive because this videocard is probably masked by using profile, also mesa required libdrm with lima support(by portage logic). libdrm has no lima support (VIDEO_CARDS=“lima”) but as i remember lima was switched for using amdgpu scheduler (which is definetly masked in arm profile see /usr/portage/profiles/arch/arm/use.mask).
I want to try create repo with correct flags etc, for now - without succes (reading manuals )
No only 5.4-main…it uses mali driver from linux. Before 5.3 you need to add lima manually, change it (at least changes i did) and include it or build separately
Can somebody please message me with details on how I can get my configurations to you? I already solved all of this, including X11. Driver works perfectly - it’s just slower than it should be. Both GL under fbcon and GL under X11 work with the lima driver - you can even get things like MythTV working.
I have build scripts, research, config files - somebody send me their email address.
the R2 Mali450 does not have a PMU and it does have 8 units, each PP is a dual unit on a mali - hence pp0 through pp3.
All you had to do was look at the DTSI for another board that ALSO has a Mali-450 MP4 and this all would of been obvious.
I’ve not exactly maintained a GIT tree I’ve just pulled all I needed, modified all I needed and then compiled it all. I can send you all the scripts I wrote to help? but you’ve already solved most if not all of the issues. I’ve got meson build scripts, the modifications to mesa (you basically find every instance of exynos (which is another similar board) and duplicate it as ‘mediatek’ in order to get your mediatek shim.
Let’s see - build Lima as a module (adding the dtsi extensions as provided by ryder lee?) - didn’t have a single issue with the detection and setup of the Mali, I sent my DTSI to frank at some point I’m sure - again it was just changes pertaining to an entry entitled ‘g3d’ or something along those lines.
I was having issues with performance but I believe you’ve solved that with optimization flags as well as disabling the debug logging for the driver?
I posted this all working in this thread aaaaages ago but if there’s anything I have that’s still useful? just message me an address to send it to.
I’m going to be integrating all the changes into franks latest version and then building lima with the optimizations and without logging - the figures you reported were much better than the performance I was getting - as long as it can spit out a frame in less than 16ms? that’ll suit me. I think the lima guys have video being hardware scaled already but for simple bi-linear scaling for emulators? Lima is capable - just need the speed!
Hey @frank-w, what is the current status of lima patches for your repos? Which branches are up to date to use if I would have a chance to give this a test?
What’s about the DTB regulator vs. board specific function in drm driver story conclusion? Am I correct that neither you nor other people in this thread were able to find how to power on/off GPU using DTB-only approach?
Also I’ve seen report from @DeadMeat that module initialization depends on the HDMI port being connected to some powered on device. Is it really the case? Had it been reproduced by other users?
I’m thinking about trying to move from serial console to netconsole in u-boot and EFI grub2 plus normal HDMI console in linux - it will be easier to maintain boards in production with setup like this.
Ah, and yet another question: am I correct that to get text console working I need to have fbcon enabled, kmsconsole fb emulation enabled and working drm driver (lima in our case)? I’m wondering if it possible to have linux console working for BPi-R2 with some other driver than lima.
And while we’re at it - have anyone had any luck with using proprietary driver from ARM for utgard GPUs?