Dear Wofgang,
-----Original Message----- From: Wolfgang Denk [mailto:wd@denx.de] Sent: Wednesday, November 03, 2010 4:58 PM To: V, Aneesh Cc: Reinhard Meyer; Albert ARIBAUD; u-boot@lists.denx.de; hs@denx.de Subject: Re: [U-Boot] [RFC] arm926ejs: fix jump to RAM nand_boot
Dear "V, Aneesh",
In message FF55437E1F14DA4BAEB721A458B6701706FD3137F3@dbde02.ent.ti.com you wrote:
If the preloader loads the u-boot to the location that it is built
for
everything should work fine once bss is initialized, right?
There is no such thing as a "location that it is built for", as the location in RAM may differ, depending on enabled features - for example, pRAM size or (shared) frame buffer size may change depending on environment variable settings. In the result, the location of U-Boot in RAM shifts. You cannot know the final address at build time.
Just curious. Why don't we allocate memory for such needs below the u-boot (lower address) like we do for malloc area and stack. This way the location where u-boot is relocated will only depend on the SDRAM size and size of u-boot itself, right?
Best regards, Aneesh