On 22 Nov 2019, at 00:25, email@example.com wrote:
Run-time aspects aside, I (naively?) believe using a different language enforces a much cleaner and maintainable separation between generic code and hardware specific configuration.
The Linux kernel had both - weren't board files messy because mixing up the two? With a lot of duplication? It'd be nice if someone who remembers board files could comment.
Now this doesn't come for free: just google "device tree stable ABI" - which... I think indirectly proves the point about board files.
PS: I doubt anyone would suggest using C code for (K)configuration.