Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#977441: linux: Pls. consider CONFIG_DRM_V3D

1 view
Skip to first unread message

Ryutaroh Matsumoto

unread,
Dec 15, 2020, 1:50:02 AM12/15/20
to
Source: linux
Version: 5.9.11-1
Severity: wishlist

Dear Maintainer,

From 5.10, Linux vc4 driver starts supporting Raspberry Pi GPU as
https://www.phoronix.com/scan.php?page=news_item&px=RPi4-Display-Linux-5.10-Coming

From Ubuntu kernel experience, CONFIG_DRM_V3D seems necessary to
fully use its hardware acceleration, as
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876

Could you consider to enable CONFIG_DRM_V3D for arm64 and possibly
for armhf?

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-4-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Ryutaroh Matsumoto

unread,
Dec 16, 2020, 6:50:02 PM12/16/20
to
Control: tags -1 + patch

Just adding CONFIG_DRM_V3D=m is not enough,
as reported at
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862/comments/5

The following patch seems necessary, which has been introduced in
the Ubuntu kernel.

change
linux/drivers/gpu/drm/v3d/kconfig
- depends on ARCH_BCM || ARCH_BCMSTB || COMPILE_TEST
+ depends on ARCH_BCM || ARCH_BCMSTB || ARCH_BCM2835 || COMPILE_TEST

Best regards, Ryutaroh Matsumoto

Debian Bug Tracking System

unread,
Dec 16, 2020, 6:50:02 PM12/16/20
to
Processing control commands:

> tags -1 + patch
Bug #977441 [src:linux] Pls. consider CONFIG_DRM_V3D
Added tag(s) patch.

--
977441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Ryutaroh Matsumoto

unread,
Dec 16, 2020, 11:20:03 PM12/16/20
to
Control: retitle 968181 GPU/DRM acceleration unavailable on Raspberry Pi

I modprobe'ed v3d.ko on vanilla Linux kernel 5.10.1,
but /dev/dri/render* does not appear like

https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/comments/14
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/comments/33

Simply compiling and loading v3d do not seem to enable
DRM/GPU acceleration on RPi4... We may need some work for enabling GPU
acceleration on Raspberry Pi series...
Ryutaroh

Debian Bug Tracking System

unread,
Dec 16, 2020, 11:20:04 PM12/16/20
to
Processing control commands:

> retitle 968181 GPU/DRM acceleration unavailable on Raspberry Pi
Bug #968181 [src:linux] linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B
Changed Bug title to 'GPU/DRM acceleration unavailable on Raspberry Pi' from 'linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B'.

--
968181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968181

Diederik de Haas

unread,
Jun 3, 2022, 7:30:02 AM6/3/22
to
On 17 Dec 2020 Ryutaroh Matsumoto <ryut...@ict.e.titech.ac.jp> wrote:
> I modprobe'ed v3d.ko on vanilla Linux kernel 5.10.1,
> but /dev/dri/render* does not appear like
>
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/comments/14

That comment mentions the following kernel config options:
> CONFIG_CLK_RASPBERRYPI=y
> CONFIG_ARM_RASPBERRYPI_CPUFREQ=y

Those are now available in Debian kernels, although the latter is '=m'.

> CONFIG_DRM_V3D=m

I have made a branch where that is (also) enabled ...

> Simply compiling and loading v3d do not seem to enable DRM/GPU acceleration
> on RPi4... We may need some work for enabling GPU acceleration on RPi series.

The major missing piece AFAICT was enablement in DeviceTree. Recently a patch
set was submitted that seems to contain the missing pieces and I added that to
https://salsa.debian.org/diederik/linux/-/commits/rpi-enable-v3d

https://lore.kernel.org/all/20220601110249.56...@gmail.com/ is
the upstream thread where I got the patches from.
If you can build a kernel based on my branch and verify it then works, that
would be great. Especially if you could send a "Tested-By <you>" email to that
upstream thread which should help in getting the patch set accepted and
eventually land in Linus' tree.

Cheers,
Diederik
signature.asc

Diederik de Haas

unread,
Aug 12, 2022, 9:50:02 AM8/12/22
to
On Friday, 3 June 2022 13:21:17 CEST Diederik de Haas wrote:
> The major missing piece AFAICT was enablement in DeviceTree. Recently a
> patch set was submitted that seems to contain the missing pieces ...
>
> https://lore.kernel.org/all/20220601110249.56...@gmail.com/ is
> the upstream thread where I got the patches from.

This patch series is now part of Linus' tree, so will be part of 5.20/6.0.
signature.asc

Debian Bug Tracking System

unread,
Sep 27, 2022, 2:10:03 PM9/27/22
to
Your message dated Tue, 27 Sep 2022 18:00:09 +0000
with message-id <E1odEsL-...@fasolo.debian.org>
and subject line Bug#977441: fixed in linux 6.0~rc7-1~exp1
has caused the Debian Bug report #977441,
regarding Pls. consider CONFIG_DRM_V3D
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


--
0 new messages