On Apr 22, Arnd Bergmann wrote: > On Friday 18 April 2014, Ley Foon Tan wrote: > > Are these all synthesized devices, or is there also some hardwired > logic? It often makes sense to split out the reusable parts into > a separate .dtsi file that gets included by every implementation. > In case you are not aware of this, devicetree files for Nios-II SoCs are produced through an automated tool calle sopc2dts: http://www.alterawiki.com/wiki/Sopc2dts http://git.rocketboards.org/sopc-tools.git/ You feed it with a sopcinfo file (AFAIK, Altera's specific format) and you obtain a full-fledged devicetree source file. Usually it works out-of-the-box, although I like to go over it and fix ranges, whitespaces, and do some cleaning. So I'm wondering -given we have such superb tool- why would we want to include the devicetree source's in the kernel? First, we'll be only supporting a *specific* configuration. Second, the dts is trivially easy to obtain. The binding documentation should be enough specification, and there's no need for further reference or examples. -- Ezequiel García, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
