On Fri, 30 Jan 2015 12:00:16 +0100 Sebastian Hesselbarth <sebastian.hesselbarth@xxxxxxxxx> wrote: > Adapting the .config and removing drivers is actually not an option. > IMHO, introducing DT was meant for a single multi-arch kernel that > can be shipped with common Linux distros. Therefore, DT is the place > you enable/disable available resources. You leave most of the SoC (and > SoM) nodes disabled as long as you cannot tell if there is a > corresponding connector available. Well, I don't know too much about the hardware, and less about the hardware modules (SoM?). As seen in the Compulab documents, there are a lot of hardware modules. For the DT, do you mean that there would be as many .dts's as the whole number of connection possibilities? I'd have better seen the inverted case as the actual empty cm-board dts: enable every option in the (generic) .dts and let the vendor/user create a specific .dts from this one for the board according to the installed modules. In any case, any real cm-a510 board should work with the generic/full .dts even if some hardware modules are lacking. No? -- Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/ -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
