Scott --
Thanks for the quick reply / review!
On 04/30/2013 12:15 PM, Scott Wood wrote:
[The devtree approach] might be OK for a new board, but adding it now
means that people using existing device trees won't get the
workaround. It might be better to just put the knowledge in platform
code.
That would be fantastic, if I knew what to test.
If you look at the thread from last year, it seems that even there in
Freescale, nobody knows exactly what triggers this.
There was the "orphan" config value, and I simply turned that into a
devtree switch.
If you can find an answer inside Freescale, I can try to respin the
patch to accommodate that knowledge. But until then, this is the best I
can do.
(And it's not a new board -- it's based on the 8315ERDB, and the
orphaned symbol is apparently related to another 8315 board that never
got released?)
Please use standard Linux coding style,
Huh. I thought I had. I'll double-check.
and submit the patch inline rather than as an attachment (e.g. use git
send-email).
Will see if I can do so. I don't actually have any sort of MTA set up
on this machine, hence these Thunderbirded messages.
Thanks again,
Anthony Foiani
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
