diff options
| author | Simon Glass <sjg@chromium.org> | 2013-12-26 16:26:24 -0700 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2014-01-14 09:01:05 -0500 |
| commit | c5cbe1e299b60063e43a9008e85df95c8006d28f (patch) | |
| tree | 55411cfcb023796260ca018b5505950b31efcf05 /board/cray/L1 | |
| parent | c9b0fa310ccc735f11afe52d3b14021c607931e4 (diff) | |
| download | u-boot-imx-c5cbe1e299b60063e43a9008e85df95c8006d28f.zip u-boot-imx-c5cbe1e299b60063e43a9008e85df95c8006d28f.tar.gz u-boot-imx-c5cbe1e299b60063e43a9008e85df95c8006d28f.tar.bz2 | |
bootm: Reinstate special case for standalone images
For standalone images, bootm had a special case where the OS boot function
was NULL but did actually exist. It was just called manually.
This was removed by commit 35fc84fa which checks for the non-existence of
this function before the special case is examined.
There is no obvious reason why standalone is handled with a special case.
Adjust the code so that standalone has a normal OS boot function. We still
need a special case for when the function returns, but at least we can
avoid the main problem.
This is intended to fix the reported:
ERROR: booting os 'U-Boot' (17) is not supported
but needs testing.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'board/cray/L1')
0 files changed, 0 insertions, 0 deletions