On 11/07/2016 09:44 PM, Yao Yuan wrote:
On 11/08/2016 12:46 PM, York Sun wrote:
On 11/07/2016 07:52 PM, Yuan Yao wrote:
From: Yuan Yao yao.yuan@nxp.com
Signed-off-by: Yuan Yao yao.yuan@nxp.com
Changed in v2: Move the readme for QSPI deploy out of only for ls2080aqds.
.../arm/cpu/armv8/fsl-layerscape/doc/README.deploy | 44 ++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy
diff --git a/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy new file mode 100644 index 0000000..25813b3 --- /dev/null +++ b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy @@ -0,0 +1,44 @@ +Boot source support Overview +-------------------
- LS1043A
LS1043AQDS:QSPI, SD, NOR, NANDLS1043ARDB:SD, NOR, NAND
- LS2080A
LS2080AQDS:QSPI, SD, NOR, NANDLS2080ARDB:NOR, NAND
- LS1012A
LS1012AQDS:QSPILS1012ARDB:QSPI
- LS1046A
LS1046AQDS:QSPI, SD, NOR, NANDLS1046ARDB:QSPI, SDIf you plan to add all SD/NAND/QSPI into this document, it is OK to call it README.deploy. Otherwise it may be better to name as README.qspi.
I'm not be familiar with SD/NAND boot. So should I rename as README.qspi? Or just keep it but waiting for some others to add SD/NAND boot in another patch?
We already have NAND boot explained in other document. Stick with the procedure you are trying to explain. Keep it simple and we can expand it when necessary. York