Dear Daniel, In message <50893633.6070...@gmail.com> you wrote: > > Overwrites must be addressed in the first place. The most common example > is that a more generic part (the module tree) registers all details > about a peripheral up-front but then sets its status to 'disabled'. That > way, the more specific part (the base board tree) can overwrite this > property to 'okay' at wish to enable it and not care for the pre-defined > details. This is also how we do things in our device-trees.
Agreed. > > I definitely can see the benefit of such a feature and would be happy > > if you could go forward and implement it. > > Ok then. I guess this should be something that can eventually be merged > back into libfdt? I can't speak for the FDT custodian, but I think this makes a lot of sense. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de When the bosses talk about improving productivity, they are never talking about themselves. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
