I have now built and run a kernel with:
CONFIG_DRM_V3D=m
CONFIG_CLK_RASPBERRYPI=y
CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
in .../focal/debian.raspi/config/config.common.ubuntu and i can confirm
that it fixes the problem.
My debug code shows raspberrypi_clk_probe() successfully adding clock
"firmware-clocks" and v3d_platform_drm_probe() now succeeding.
/dev/dri/renderD128 exists.
A simple opengl test program renders correctly and reports:
renderer = V3D 4.2
whereas before this change, it reported:
renderer = llvmpipe
Note that this is a 32-bit kernel, based on the code in the raspi
branch, which is at kernel version 1009. I don't know if the same
changes will also work in 64-bit kernels. A recent post in raspberry pi
forums suggests it may not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880125
Title:
v3d driver clock problem forces OpenGL to use software rendering
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
