On Tuesday, September 14, 2010 08:40:55 Stefan Roese wrote: > 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.
there should at least be a build system unification if the general source code isnt possible. all Blackfin builds now (LDRs) have a dedicated binary to initialize memory before any of u-boot is loaded. this is the "initcode" stuff in the blackfin cpu dir. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
