From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcmVhcyBCaWXDn21hbm4=?= Date: Thu, 16 Jun 2011 15:10:16 +0200 Subject: [U-Boot] SPL framework re-design In-Reply-To: References: <4DF9B9E0.8020206@ti.com> <20110616104716.762DD19E5AC3@gemini.denx.de> Message-ID: <4DFA00B8.7000807@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear all, Am 16.06.2011 14:55, schrieb Daniel Schwierzeck: > On Thu, Jun 16, 2011 at 12:47 PM, Wolfgang Denk wrote: >> Dear Aneesh, >> We should try to get rid of the need to create symbolic links. If we >> use the same source files as for the "normal", then we should also >> use the normal object files. > > By using something like CONFIG_UBOOT_SPL_BUILD in the make environment > and as CFLAG all code can be reused without symlinking or copying. > You need only a separate directory for putting the object files in. +1 for reusing existing stuff but changing it a little bit to be able to work as spl(driver) where this is necessary >>> 2. How do we handle the type of SPLs that handle different media. For >>> instance omap3 spl will support mmc and NAND. Can we have a directory >>> tree starting with 'spl/'? If so, how does this tree share generic code >> >> Yes, this makes a lot of sense to me - see above. >> >>> available in media specific directories such as nand_spl/ and mmc_spl/. >>> Symbolic links? >> >> No. Let's put this stuff into spl/common/ > > To use the spl directory as remote build directory, the obj and src variables > must be tweaked a little. To keep this changes minimal, it is not possible to > have further source files and directories inside the spl directory. I suggest to > put common spl code in TOPDIR/lib/spl/common, TOPDIR/lib/spl/nand and so on. sounds better to me than having a complete new tree under /spl regards Andreas Bie?mann