Scott Wood <scottw...@freescale.com> writes: > Board information is available from the device tree, and from > platform code that was selected based on the device tree.
You're right, of course; I was focusing on discovery/probing, and completely forgot about "provided information". However, as I just mentioned in my reply to Yang, I'm pretty happy with the kconfig solution (Adrian's patch, basically). If we find that this is a more widespread problem, we can revisit this discussion; but if only a handful of us have encountered this in a 5-year-old design, then I don't think it's worth the extra effort of making it dynamic. Maybe someone who knows devtree really well could crank that out in a few minutes... but I'm not that person. :) Regardless, thanks very much for helping out on this. I do advocate that Adrian's patch get put into place, so that we don't have undocumented / unconnected kconfig symbols in the tree. If we ever do find out more details about the workaround, we can at least add some comments at the code site. Thanks again! Best regards, Anthony Foiani _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev