> On 11/02/2011 08:56 PM, Marek Vasut wrote:
> > +   onenand_spl_load_image(CONFIG_SPL_ONENAND_LOAD_ADDR,
> > +                           CONFIG_SPL_ONENAND_LOAD_SIZE,
> > +                           (void *)CONFIG_SYS_TEXT_BASE);
> 
> If we make it "nand_spl_load_image", and make the #defines conform, we
> can have the same code call the function for nand and onenand.  I don't
> see any reason why onenand is a completely different subsystem in
> general, rather than just another NAND driver.  The NAND subsystem's
> driver interface is lower level than it should be, but that affects
> other NAND controllers as well (such as fsl_elbc).
> 
> Switching to the generic nand_boot() in
> http://patchwork.ozlabs.org/patch/123219/ would get you the ability to
> load the environment during the SPL.
> 
> -Scott

I don't think I understand. Why do you want to mix onenand and nand ? Also, 
will 
your approach still allow me to squeeze the important code into the first 1kb 
for the initial copying of SPL?
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to