summaryrefslogtreecommitdiffstats
path: root/doc/README.ramboot-ppc85xx
diff options
context:
space:
mode:
Diffstat (limited to 'doc/README.ramboot-ppc85xx')
-rw-r--r--doc/README.ramboot-ppc85xx10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/README.ramboot-ppc85xx b/doc/README.ramboot-ppc85xx
index 8ed45fb46d..5cc546a36f 100644
--- a/doc/README.ramboot-ppc85xx
+++ b/doc/README.ramboot-ppc85xx
@@ -23,11 +23,11 @@ methods could be handy.
the board.And then execute the bootloader from DDR.
Some usecases where this may be used:
- While developing some new feature of u-boot, for example USB driver or
- SPI driver.
- Suppose the board already has a working bootloader on it. And you would
- prefer to keep it intact, at the same time want to test your bootloader.
- In this case you can get your test bootloader binary into DDR via tftp
- for example. Then execute the test bootloader.
+ SPI driver.
+ Suppose the board already has a working bootloader on it. And you would
+ prefer to keep it intact, at the same time want to test your bootloader.
+ In this case you can get your test bootloader binary into DDR via tftp
+ for example. Then execute the test bootloader.
- Suppose a platform already has a propreitery bootloader which does not
support for example AMP boot. In this case also RAM boot loader can be
utilized.
OpenPOWER on IntegriCloud