You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read the fakevc4-fkms-v3d video driver still enables access to the dispmanx API. Whereas the vc4-kms-v3d driver, the default I believe, no longer supports the dispmanx API.
Could anyone confirm if the vc4-fkms-v3d (f is for fake) driver enables the dispmanx API to live on for a while yet, at least?
I ask because it would be great to get dispmanx_vnc ported to newer systems that default to the vc4-kms-v3d driver and thus claim the likes of dispmanx_vnc have no future.
The text was updated successfully, but these errors were encountered:
@inspector71, I don't have a definitive answer. I have no affiliation with the Raspberry Pi companies.
I suspect that FKMS will not be supported in the long term. The Raspberry Pi 5 cannot use FKMS. There is no way to use DispmanX on a Raspberry Pi 5, so I don't think there will be a reason to keep supporting FKMS. This is just a guess and you might get a better answer by asking on the Raspberry Pi forum.
I am no longer developing this repository and I am thinking of archiving it.
I read the fake
vc4-fkms-v3d
video driver still enables access to thedispmanx
API. Whereas thevc4-kms-v3d
driver, the default I believe, no longer supports thedispmanx
API.Could anyone confirm if the
vc4-
fkms-v3d
(f
is for fake) driver enables thedispmanx
API to live on for a while yet, at least?I ask because it would be great to get
dispmanx_vnc
ported to newer systems that default to thevc4-kms-v3d
driver and thus claim the likes ofdispmanx_vnc
have no future.The text was updated successfully, but these errors were encountered: