On Tue Nov 02, 2010 at 12:16:55PM +0100, Albert ARIBAUD wrote: > Le 02/11/2010 10:56, Sughosh Ganu a écrit : >> hi Albert, >> >> On Tue Nov 02, 2010 at 10:47:49AM +0100, Albert ARIBAUD wrote: >> >>> Now a solution would be that the actual u-boot size be flashed along >>> with it, for instance as a literal defined as '.word _end - _start' >>> right after the vectors. The SPL could load a first NAND block, read the >>> literal, round it to a multiple of NAND blocks by default, and then read >>> this quantity. >>> >>> That would remove the dependency at the cost of extra code in the SPL, >>> though, and not all boards might be able to afford it. >> >> Another issue is that the nand_spl might be compiled and flashed >> to the NAND as a separate entity, using a separate flashing >> mechanism. If we use the dynamic calculation of the u-boot size, >> this would necessitate building and flashing the nand_spl each time >> along with u-boot. > > Not with the solution I describe, as the once-flashed SPL would fetch > the actual size from the actual u-boot.
Yes that is correct. I was referring to the other solution of fixing the size through the script. -sughosh _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
