There are farmers who join agricultural co-ops to do similar things. I've seen few operate differently - the co-op owns the machines and maintains a bunch of operators. These are requested by farmers who want work done - spraying, tilling, harvesting, etc.
That's untrue. I know a farmer, who buys a John Deere combine before harvest. It stays unused until his harvests are done, and returns it by end of harvest season incurring $30k on this entire transaction. Why does he do that? Because he has two weeks to finish up harvesting or start incurring losses on his harvest. Farmer does care about saving costs/losses AND getting the job done in time.
This is a great initiative. However, I feel that "no-tech" shouldn't be a target and that isn't necessarily good. Ex. Precision tech helps reduce operator fatigue and increases efficiency with respect to equipment operation time and material used.
This isn't to say that tech can't be shoved in every other panel on the tractor - but hope this drives Big companies towards considering where tech is necessary and where it's not.
> However, I don't like new files as patches. I really prefer to have my device tree be a dts file that I bring in instead of bundled into a patch. Maybe I'm not following the guidelines, but I think it's nicer to be able to search for dts things in .dts files and I get nice syntax highlighting and whatnot.
This is what I do on custom boards. It's better to "look" at files and link to others when they're files and not patches.
A lot of work here is working on vendor provided BSP (which can range from esoteric mix of ancient kernels/bootloaders to top-quality community maintained mainline kernels) to work on your custom board/product.