From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Roese Date: Tue, 14 Sep 2010 14:40:55 +0200 Subject: [U-Boot] Multiple binaries built through u-boot source In-Reply-To: <4C8F4CB5.6050107@st.com> References: <4C8F0682.2080006@st.com> <201009140916.39313.sr@denx.de> <4C8F4CB5.6050107@st.com> Message-ID: <201009141440.55577.sr@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Vipin, On Tuesday 14 September 2010 12:21:41 Vipin Kumar wrote: > > Take a look at the NAND_SPL infrastructure (nand_spl/*). It was created > > for platforms booting from NAND with tight restrictions (e.g. 4k image > > size for inital setup, mostly DDR). General idea here is that 2 images > > are created: > > > > a) Very small SPL (secondary program loader) image with only basic > > > > setup, like DDR and NAND > > > > b) RAM based U-Boot image > > > > Both images are combined in the build process creating a single image > > that can be flashed into NAND. > > > > doc/README.nand-boot-ppc440 might be interesting to get some more infos > > about this, some of it PPC4xx specific though. > > Yes, got it. The only point is that this is meant to boot from NAND, > ONENAND devices(As the name suggests). Can there be a generic interface > independent of a particular device. > > Offcourse I agree that execute in place would work for NOR devices and we > wont need this kinda solution but still a generic solution for both types > of devices is preferable Sure, a more generic approach would be better. But I suspect that this is not so easy to do. Those tight image-size restrictions of the IPL/SPL loaders will make such generalisation efforts quite difficult. Cheers, Stefan -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de