I have not tried it for non-NAND boot, but it should work for any type of boot devices where gd->reloc_off is set properly.
The previous version still works for nay NOR boot, as the non-relocated pointers to static strings are always point to the RO data in the NOR. But for the NAND boot where we start directly from RAM, this happens, because the initial non-relocated memory can be overwritten any time... Best regards, Valeriy Glushkov P.S. Sorry for the invalid email address. Fixed. ----- Original Message ----- From: "Jean-Christophe PLAGNIOL-VILLARD" <plagn...@jcrosoft.com> To: "Valeriy Glushkov" <g...@lstec.com> Cc: <u-boot@lists.denx.de> Sent: 19 ?????? 2009 ?. 15:05 Subject: Re: [U-Boot] [PATCH] NAND: cmd_nand.c: fix invalid pointers tostatic relocated chip names > On 15:13 Mon 19 Jan , g...@horse.lst.loc wrote: >> When U-boot starting from NAND the pointers to chip names are set before >> relocation. >> If the original memory block is overwritten after relocation that led to >> invalid >> string data in the nand utility. > > what will happen when it does not start from nand but an other device?? > > btw please fix you mailer to show your real address in the From > > Best Regards, > J. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
