jvanthienen-gluo

Tried implementing it. It still needs testing. I'm currently trying to build a custom image for testing the v3d functionallity. Relevant pkgs PR: https://github.com/siderolabs/pkgs/pull/1182 Relevant extensions PR: https://github.com/siderolabs/extensions/pull/643

I can't seem to get the GPU to work (getting `/dev/dri` to be available). There is probably and hopefully something small I'm looking over. I enabled the usage of `vc4`...

Good point, I didn't do that yet. But that doesn't explain why running a kernel with build-in `vc4` and `v3d` doesn't work either? Build-in kernel config: ``` # kernel/build/config-arm64 CONFIG_DRM_V3D=y...

I’m working on this system extension for Talos Linux to add `dtoverlay=vc4-kms-v3d` to the Raspberry Pi’s `config.txt` file for GPU support. What’s the recommended approach for implementing this as an...

Yes that is correct, I currently do the following in the profile for the imager, and this works: ```yaml ... overlay: name: rpi_generic image: imageRef: ghcr.io/siderolabs/sbc-raspberrypi:v0.1.3 options: configTxtAppend: dtoverlay=vc4-kms-v3d ......

Ok I see, so it's on the image level only, no way around it? Maybe it's a better idea to create 2 targets for the raspberry pi 4 then? One...

Alright, firmware wise this is indeed fine for now. Only issue is that a user cannot (conveniently) add the extra overlay options from within Omni and only via the Imager...

Update: Relevant pkgs PR: https://github.com/siderolabs/pkgs/pull/1196 Relevant extensions PR: https://github.com/siderolabs/extensions/pull/659 Relevant docs PR: https://github.com/siderolabs/talos/pull/10622

I pushed the changes also to the v1.10 docs