-----Original Message----- From: Wood Scott-B07421 Sent: Thursday, June 27, 2013 6:33 AM To: Zhang Ying-B40530 Cc: u-boot@lists.denx.de; afleming@gmail.com; Xie Xiaobo-R63061; Zhang Ying-B40530 Subject: Re: [PATCH 6/7 v6] nand: tpl : introduce the TPL based on the SPL
On 06/26/2013 02:18:31 AM, ying.zhang@freescale.com wrote:
From: Ying Zhang b40530@freescale.com
Due to the nand SPL on some board(e.g. P1022DS)has a size limit, it can not be more than 4K. So, the SPL cannot initialize the DDR with the SPD code. This patch introduces TPL to enable a loader stub that runs in the L2 SRAM, after being loaded by the code from the SPL. It initializes the DDR with the SPD or other operations.
The TPL's size is sizeable, the maximum size must not exceed the size of L2 SRAM.
Using L2 SRAM for this is an implementation detail, and not appropriate for a description of the generic TPL infrastructure. For example, on newer QorIQ chips you'd be using CPC (L3) SRAM.
It initializes the DDR through SPD code, and copys final uboot image to DDR. So there are three stage uboot images:
- spl_boot, * tpl_boot, * final uboot image,
This patch is on top of the patch: SPL : spi flash : support to start from eSPI with SPL
You don't need to mention a dependency on an earlier patch in the same patchset (and when you do need to mention a dependency, it should be below the --- line so it doesn't go into the git history). OTOH, you do need to mention the dependency on the patch to have a separate autoconf.mk. [Zhang Ying] I want to know when the patch that creates a separate autoconf.mk can be merged? My patch need to be verified on the basis of it.