From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 28 Jun 2011 11:18:41 -0500 Subject: [U-Boot] SPL framework re-design In-Reply-To: <4E097A93.6020900@ti.com> References: <4DF9B9E0.8020206@ti.com> <20110616104716.762DD19E5AC3@gemini.denx.de> <4DFA00B8.7000807@gmail.com> <20110627092731.3532D202C61@gemini.denx.de> <20110627133435.31cd3271@schlenkerla.am.freescale.net> <20110627205046.BF6FB177DBA4@gemini.denx.de> <20110627155535.4217b15b@schlenkerla.am.freescale.net> <20110627211033.783351A23C39@gemini.denx.de> <20110627161803.16783c48@schlenkerla.am.freescale.net> <20110627212200.76E8316A1C77@gemini.denx.de> <4E097A93.6020900@ti.com> Message-ID: <20110628111841.0f83f428@schlenkerla.am.freescale.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, 28 Jun 2011 12:24:11 +0530 Aneesh V wrote: > 1. If there are SPL customized generic files like the > nand_spl/nand_boot.c where do we keep them? I suggest that we keep them > in spl/nand, spl/onenand etc. And for the object file hierarchy let's > have something like spl/obj. How about that? How about drivers/nand/generic_spl.c, drivers/nand/fsl_elbc_spl.c, etc.? -Scott