Dear Benoît, In message <5617c8b9.30...@wsystem.com> you wrote: > > Currently, it's all mixed up between CONFIG_SYS_LOAD_ADDR, the loadaddr > environment variable and the load_addr global C variable. > > The 1st issue is that loadaddr and load_addr currently diverge if the user > changes loadaddr or if commands change load_addr. > > The 2nd issue is that some commands use the value of loadaddr as a default, > whereas others use load_addr. And if that fails, CONFIG_SYS_LOAD_ADDR is > sometimes used as a fallback value. > > The 3rd issue is that some read/load commands set load_addr, but not all > (e.g.: > mmc read, ext2load), which breaks the whole feature, but fixing this could > break > existing configurations relying on the current behavior.
Thanks for the analysis. As always, patches are welcome :-) Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de Time is an illusion perpetrated by the manufacturers of space. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
