On Thu, Apr 23, 2009 at 12:03:06PM -0500, Scott Wood wrote: > Anton Vorontsov wrote: >> On Thu, Apr 23, 2009 at 11:00:48AM -0500, Scott Wood wrote: >>> Even if the given change may not break the firmware, it could force an >>> update in which a prior change breaks the firmware. >> >> I'm not sure I'm following here. Could you give an example? > [...] > Device tree Z2 goes in kernel Y2. It > will break when used with u-boot X1,
This is exactly what we should try to avoid. We should not accept any changes that might break older firmwares. That is, keep the device tree workable with X1 and X2, by any means. For example, if X1 looks for "/soc8...@..." name instead of compatible entry, we'll have to live with the name forever, but we should be free to switch Linux so that it'll use only the "compatible" property matching. If X1 looks for "/soc8...@..." and X2 looks for "/s...@...", so that Z1 and Z2 aren't compatible at all, then we're in trouble. But we're in trouble regardless of what Linux is doing, no? -- Anton Vorontsov email: cbouatmai...@gmail.com irc://irc.freenode.net/bd2 _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
