Hi users of meta-raspberrypi,
I'd like to ask around if for you people vc4-kms-v3d (opposed to vc4-fkms-v3d)
*really* is the working way to get vc4 support on a Raspberry Pi 4 Model B.
Both on master and kirkstone, vc4-kms-v3d is the default. It's defined in
/conf/machine/raspberrypi4-64.conf:
VC4DTBO ?= "vc4-kms-v3d"
I was mildly surprised to find this, because on my system (running Kirkstone) I
can get the screen to work only if I specify vc4-fkms-v3d.
Commit a6fa6b3aec36b92c3750852dd6788af9d2ce08f6 [1] broke my build. The commit
message further suggests that vc4-Fkms-v3d is broken, while vc4-kms-v3d is not.
So I'm wondering:hy is it exactly the other way round on my machine?
raspberrypi4: Use full kms (vc4-kms-v3d) DT overlay
With latest 5.10 kernel fkms version fails to bring up VC4 and we do not
get dri device initialized ( /dev/dri ) is empty, which means we can not
launch wayland componsitors.
Best regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60421): https://lists.yoctoproject.org/g/yocto/message/60421
Mute This Topic: https://lists.yoctoproject.org/mt/99727959/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
