gtk4 extension on armv7l (RaspberryPi)

[Paul_123]

Yes, pi4 with 32bit userspace, defaults to the aarch64 kernel, due To the memory management problems with the armv7l kernel.  This is what RaspiOS does too.

You just have to be a little careful compiling 32bit apps.

[yvs]

Using vc4-kms-v3d

Xorg-3d works without problems on the RPi4:

just to note:
- vc4-kms has different underlying parts for pi4 and pi3
- code path is distinct for hdmi and dsi screens

from my experience firmware v4-fkms is more likely to work without issues (for example vc4-kms-v3d doesn't work correctly in most cases with pi3b+ and dsi screen that I have)

[yvs]

Xorg-3d works without problems on the RPi4:

Code: [Select]

glxinfo | grep Acc
    Accelerated: yes

inxi -b
System:
  Host: boxrpi4_32 Kernel: 6.6.34-piCore-v8 arch: aarch64 bits: 64
  Desktop: FLWM v: N/A Distro: piCore 15.0
Machine:
  Type: ARM System: Raspberry Pi 4 Model B Rev 1.2 details: N/A rev: c03112
    serial: 100000002f7ed527
CPU:
  Info: quad core Model N/A [MCP] speed (MHz): avg: 1000 min/max: 600/1500
Graphics:
  Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A
  Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A
  Device-3: bcm2711-vc5 driver: vc4_drm v: N/A
  Display: server: X.org driver: X: loaded: modesetting dri: vc4
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    resolution: <missing: xdpyinfo/xrandr> resolution: 3840x2160
  API: OpenGL v: 3.1 vendor: broadcom mesa v: 24.1.4 renderer: V3D 4.2.14..and gtk4-widget-factory is noticeably quicker.

on this rpi4 and gtk4.14 setup:
- in case of gtk4.14 I suppose that switching to GL rendering will give some gtk4 boost too (gtk4.14 default ngl is slower than gl)
- gtk4.x with vulkan rendering (if it's supported there) can give even more boost (it matches or surpasses gl, tradeoff of that: vulkan is not so rich in api like gl)

p.s. "faster/slower" is accordingly to gtk4 notes on new renderers

[Juanito]

from my experience firmware v4-fkms is more likely to work without issues (for example vc4-kms-v3d doesn't work correctly in most cases with pi3b+ and dsi screen that I have)

I never had any problems with vc4-kms-v3d up to and including 14.x…

I suspect there’s a problem with the vc4 kernel driver on RPi3 in 15.x, but can’t figure out how to isolate it.

[yvs]

from my experience firmware v4-fkms is more likely to work without issues (for example vc4-kms-v3d doesn't work correctly in most cases with pi3b+ and dsi screen that I have)

I never had any problems with vc4-kms-v3d up to and including 14.x…

I can't say about TC and hdmi, it's on other distros and with dsi screen

I suspect there’s a problem with the vc4 kernel driver on RPi3 in 15.x, but can’t figure out how to isolate it.

Have you tried it with fkms? ("dtoverlay=vc4-fkms-v3d" + "disable_fw_kms_setup=1" works on rpi3b+ tc15 xorg in my case)