looking for common practice here ... what's the canonical way that
one should add content to a .dts file for a new board -- all at once,
or broken into patches associated with corresponding .scc files that
come into play only if one selects that functionality?
i ask since i'm a big fan of modularity, but that doesn't seem to
work very well here. if i start with a baseline .dts file, and break
the rest into optional patches, then based on what a developer selects
for his build, some of those patches simply aren't going to apply very
cleanly.
it would, of course, be easier to just add everything even
potentially necessary to the single .dts file, since that's not really
adding any actual functionality, just adding more detailed information
about the target board (even if it's never used).
thoughts? am i overthinking this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
