Recommendations on building extensions with extra Kernel modules

[srgvg]

I need to install Talos on some industrial device (MiTAC MB1-10AP) which has a GPIO plugin, which Debian identifies as using the pinctrl-broxton and optionally the pinctrl-intel drivers.
Which means I need to build a custom extension into a custom installer.

My question is, should I consider doing the work as a patch to https://github.com/siderolabs/extensions ? I see there's a contrib tier, but not sure what would be accepted or not. In addition,.

If acceptable, should I build this as
a specific extention for each of these two drivers
combine both drivers into 1 pinctrl extension,
combine + and possibly allow more drivers part of the pin-control project, or also other GPIO related drivers?

I couldn't find which specific GPIO drivers are built into Pi and other SBC images. Maybe there are other places to include these drivers?

[frezbo]

just as separate for now or you could also do a meta extension that pulls in both, so have different options to select from, PR's are welcome

[srgvg]

I'm confused about the different patterns (?) for extensions; I had a PR that enables some new vanilla kernel drives/ modules. Am I correct to think, such an addition does not need an extension (in the sense that you can add it via the factory), but only need to enable the drivers? Adding a layer through the factory would only be needed for out of tree extra modules? If that is not correct: My PR was merged before the 1.12 release, but that new driver is not listed in the factory. Maybe extensions have a separate release workflow, and that wasn't done yet?

The implemented patches are siderolabs/pkgs#1388 and siderolabs/extensions#907

Looking at the digest list in e.g. ghcr.io/siderolabs/extensions:v1.12.1 doesn't show the gpio-pinctr extension

Looking at ghcr.io/siderolabs/gpio-pinctrl only shows alpha released image for 1.12.0 and 1.13.0

It seems I'm missing some step to have this built into the full eco-system?

[smira]

I'm confused myself why it hasn't been published (it should have been)

[smira]

I guess it was a mis-merge at some point, but we'll get it back for v1.12.2