Jon Loeliger wrote:
Scott Wood wrote:
Paul Gortmaker wrote:
OK, so does that mean that the cuboot wrapper is explicitly
not supported for all the 83xx, 85xx, and 86xx boards?
No (except 86xx, which doesn't have cuboot, because it never existed
in arch/ppc and thus there's no compatibility to maintain), it just
means that chosen was never added to those dts files, and thus cuboot
has no console output.
Also note that nothing stops the causal kernel booter
As opposed to the spontaneous kernel booter? :-)
from _starting_ with an arch/powerpc/boot/dts/ file,
adding a node to it, and using _that_.
The "casual" user shouldn't need to make any changes, especially for the
kernel's own dts files to work with the kernel's own wrapper.
The decision on whether to put the chosen node in the device tree should
be based on which version of u-boot it's more important to maintain
compatibility with (for some platforms, no chosen-duplicating version of
u-boot supported device trees on the platform), and what the
consequences of each form of incompatibility are (e.g. no console output
during the bootwrapper, versus no boot arguments or initrd in the kernel).
-Scott
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
