On Fri, Aug 22, 2008 at 4:37 AM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
However, the dtc code is horrible. I have sprinkled annotations all over the dtc code and I still have not figured out everything. Segher says that the current dtc upstream has better code quality, however our changes are extensive and merging will be a pain.
Our changes mostly live in the flatten tree code and the use of a new command, /config/. It would not be impossibly hard to fix.
The v3 decision is to use dts. There should only be one dts parser. So if we want to extend the use of the dts code, we modify the current parser or bring in the new one and use it. But we should not create two parsers in v3. I think that's a hard rule we can stick to.
If we brought in the new upstream, now that we know how things should work, we could do a better job. But we need volunteers. Until then, I think this interesting but far-reaching change must wait. My top priority is K8. The config system is good enough for now.
ron