Comments

Make it clear that we need to load a legacy-formatted (aka uImage)
kernel into memory as well as the DT if used before using "spl export".
Cc: Yebio Mesfin <ymesfin@ti.com>
Signed-off-by: Tom Rini <trini@ti.com>
---
doc/README.falcon | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)

Dear Tom,
In message <1403874230-31939-1-git-send-email-trini@ti.com> you wrote:
> Make it clear that we need to load a legacy-formatted (aka uImage)> kernel into memory as well as the DT if used before using "spl export".
Can this not also be a FIT image (or even a zImage)?
Best regards,
Wolfgang Denk

On Fri, Jun 27, 2014 at 09:03:50AM -0400, Tom Rini wrote:
> Make it clear that we need to load a legacy-formatted (aka uImage)> kernel into memory as well as the DT if used before using "spl export".> > Cc: Yebio Mesfin <ymesfin@ti.com>> Signed-off-by: Tom Rini <trini@ti.com>
Applied to u-boot/master, thanks!

On Fri, Jun 27, 2014 at 08:11:07PM +0200, Wolfgang Denk wrote:
> Dear Tom,> > In message <1403874230-31939-1-git-send-email-trini@ti.com> you wrote:> > Make it clear that we need to load a legacy-formatted (aka uImage)> > kernel into memory as well as the DT if used before using "spl export".> > Can this not also be a FIT image (or even a zImage)?
It cannot yet, no.

Patch

diff --git a/doc/README.falcon b/doc/README.falconindex 82a254b..e9f8a75 100644--- a/doc/README.falcon+++ b/doc/README.falcon@@ -31,9 +31,10 @@ informed to load it before running the kernel.
To boot the kernel, these steps under a Falcon-aware U-Boot are required:
1. Boot the board into U-Boot.
-Use the "spl export" command to generate the kernel parameters area or the DT.-U-Boot runs as when it boots the kernel, but stops before passing the control-to the kernel.+After loading the desired legacy-format kernel image into memory (and DT as+well, if used), use the "spl export" command to generate the kernel parameters+area or the DT. U-Boot runs as when it boots the kernel, but stops before+passing the control to the kernel.
2. Save the prepared snapshot into persistent media.
The address where to save it must be configured into board configuration