I'm using a custom-built shield including a MAX3107 SPI-to-UART converter.
I had to enable and build the max310x.c module (since it's not enabled by default, not even as a module) and write a custom device tree overlay. For convenience, I did all this on the target itself, by downloading the kernel source (rpi-source) and building against it.
However, I wouldn't want to do this again and again:
a) on every system I am currently managing (many of them)
b) every time I update the kernel using rpi-update
What do you think would be a reasonable workflow for deploying this feature in a sustainable way?
Submit my changes to https://github.com/raspberrypi/linux and hope/wait for them to be merged and rebuilt?
Fork the https://github.com/raspberrypi/firmware and push my binaries there somewhere?
Try to package my binaries as a .deb somehow? Would there be a way to make the module kernel-independent?
Even if there's a way of doing this automatically, I wouldn't want to download the whole kernel source on every system and rebuild everything again and again.
Any other ideas?