Cannot enable VC4 graphics driver on RPi 3

Bug #1655411 reported by Alberto Aguirre
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

It seems the VC4 device tree overlay is not applied by the Rpi firmware.

I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader does not apply the overlay at all.

I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility compiled by pulling pieces from (https://github.com/raspberrypi/userland and https://github.com/dgibson/dtc)
The result is here: https://github.com/albaguirre/dtmerge

With this new device tree binary blob, The VC4 driver (as a module) loads (and you can see /dev/dri/ entries)

I also played around with the tip of u-boot tree (git://git.denx.de/u-boot.git) which has support to apply device tree overlays - it applied fine and VC4 is at least recognized but the driver cannot initialize properly.

Any idea on what magic incantation is needed for the RPi loaders (start.elf etc) to apply the vc4 overlay?

description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1655411

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Oliver Grawert (ogra) wrote :

where exactly did you add the overlays in the first paragraph ? only overlays in /boot/uboot/overlays are read by the proprietary bootloader (you need to create the dir)

Revision history for this message
Oliver Grawert (ogra) wrote :

ogra@pi3:~$ cd /boot/uboot/
ogra@pi3:~$ sudo tar xvf pi2-kernel_22.snap/dtbs/overlays.tgz

then adding "dtoverlay=vc4-kms-v3d" and creating /etc/modules-load.d/vc4.conf with just "vc4" in it seems to get me vc4 loaded and i get:

[ 4.952421] vc-cma: Videocore CMA driver
[ 4.956535] vc-cma: vc_cma_base = 0x00000000
[ 4.961451] vc-cma: vc_cma_size = 0x00000000 (0 MiB)
[ 4.967083] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
[ 4.972972] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
...
[ 6.036262] vc-sm: Videocore shared memory driver
[ 6.036269] [vc_sm_connected_init]: start
[ 6.036676] [vc_sm_connected_init]: end - returning 0
...
[ 10.229614] [drm] Initialized drm 1.1.0 20060810

i assume we also need to set gpu_mem in config.txt

Revision history for this message
Alberto Aguirre (albaguirre) wrote :

Turns out we simply need to use the latest firmware loader blobs, then the vc4 overlay is applied correctly while using u-boot.

https://github.com/raspberrypi/firmware/tree/master/boot

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.