On Mon, Jul 07, 2008 at 11:23:47AM +0200, Wolfram Sang wrote: > On Mon, Jul 07, 2008 at 11:28:43AM +1000, David Gibson wrote: > > > > This function is surely needed in every case I considered so far. I am > > > just sceptical if the boot-loader can determine a correct parentoffset > > > all alone (which one of the two I2C busses is the correct one?). This is > > > > Hrm. "all alone". It's not clear to me what else there could be that > > would have more information than the bootloader. > > What I meant is that all the information a bootloader has may not be > sufficent. To solve this, some additional infos could be added to the > tree. In this case, it could be a few aliases.
My point is that the dts and the bootloader will typically be built by
the same person as part of the same process. What is the rationale
for encoding this information into the tree fragments rather than the
code?
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
signature.asc
Description: Digital signature
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
