The kms part is related to driving the display and the v3d part is related to driving the 3D hardware.
While this is the correct behaviour for a standard linux platform, and is the eventual goal for the 3D driver, it is currently an obstacle for many users.
The standard camera and video decode apps that drive the display from the gpu cannot be used when vc4-kms-v3d is enabled.
Apps that use dispmanx for overlays or performance reasons (e.g. emulators) cannot be used.
The official DSI display is not currently supported.
HDMI displays are configured differently and may not behave the same way.
So Eric has added a new mode to the driver. If you enable the usual vc4-kms-v3d driver (e.g. from raspi-config) and then edit the vc4-kms-v3d overlay to:
Code: Select all
This means that tvservice, dispmanx, omxplayer(*), raspivid etc should work as before, but you can also run desktop GL apps from X.
The one thing you cannot do with this driver is use firmware side 3D. This includes OpenVG which uses the 3D hardware from the firmware side.
To test this you will need the latest rpi-update firmware.
(*) By default omxplayer uses OpenVG for subtitles and status messages which is not compatible with this driver. Launch with "--no-osd" and it can be used for video playback.