On Wed, Apr 06, 2005 at 11:19:34PM +0200, Wolfgang Denk wrote:
My ARM experience is ... ummm... let's say limited.
Same here. Still learning and hoping future products will be MIPS based :)
Well, I think that U-Boot should not rely on a pre-configured RAM size, but automatically detect how much RAM there is on a system,
That is a bit problem. I do not know about any way how to detect memory configuration. You need to configure traffic controler to match your setup.
relocate itself to the very end of the RAM, and then set up a memory map as described in the README:
[Top of RAM]: [optional: protected RAM] [optional: framebuffer] U-Boot bss U-Boot data U-Boot text Malloc Arena Board Info Data and permanent copy of global data U-Boot stack (growing downward) ... [Bottom of RAM]
That's probably doable and I'll try to implement it this way, except that end of RAM address will have to be given in config file. Or does anyone knows any trick how to detect it?
My patch only removes limitation for malloc pool size and stack size to be directly loadable to register as a constant. Now it is probably time to think about it a bit more...
About it - about what?
About initialization code on ARMs
Best regards, ladis