Fork with custom kernel patches

[pepijndevos]

In order to support discrete AMD GPUs on raspberry pi 5 I forked this repo to use a patched kernel, config flags, and add the firmware package. It's working like a charm but I have some questions:

• would this be interesting to upstream or a too invasive change for too obscure hardware combination?
• if not, how can I provide updates to installations of my fork? Can the supervisor be configured with additional URLs to check?
• How can I ship preinstalled integrations and add-on's with my fork?
• the AMD firmware package is actually too old, how often do you update your buildroot version?
• I see a 6.12 branch, but not for Raspberry Pi. Any plans to update? Raspi does have a 6.12 branch.

[unclehack]

The 6.12 Raspberry Pi kernel would have to come from the upstream. The upstream for the Raspberry Pi kernel is from the official Raspberry Pi kernel repository. The patches or configuration changes should be contributed to the upstream Raspberry Pi kernel first.

The official Raspberry Pi kernel tree can be found at https://github.com/raspberrypi/linux.

[pepijndevos]

I don't think it is likely that these patches will make it into upstream on short notice, hence my questions about distributing my fork.

Or maybe I'm better off installing the supervisor on Debian with a custom package repo for patched software?

[unclehack]

I'm not a maintainer of the project. My feedback and recommendations are probably going to be treated like anyone else's.

Carrying the patches means the maintainers have to update them when there are changes in the upstream and to account for additional issues. They'll decide what they want to do in the end.

Perhaps you can share the patches to at least let the maintainers review them?

[pepijndevos]

This is my fork: 8023f10