> That commit was 9 weeks and 422 commits ago. At some point after that, it was > disabled again. https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/arch/arm64/configs/bcm2711_defconfig?h=raspi Well in the latest version https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/arch/arm64/configs/bcm2711_defconfig?h=raspi I see that both 'CONFIG_CLK_RASPBERRYPI' and 'CONFIG_ARM_RASPBERRYPI_CPUFREQ' are set to 'y' why do you think it was disabled again?
> Is it sufficient simply to re-enable CONFIG_CLK_RASPBERRYPI? I don't know, but the original commit also enabled CONFIG_ARM_RASPBERRYPI_CPUFREQ=y If Hui Wang meant with his comment#7[1] something different than enabling 'CONFIG_CLK_RASPBERRYPI' and 'CONFIG_ARM_RASPBERRYPI_CPUFREQ' I don't know what it is. [1] https://bugs.launchpad.net/ubuntu/+source/linux- raspi/+bug/1880125/comments/7 -- 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
