> I am somewhat new to U-Boot development. What further work would be
> required to bring this up to mainline U-Boot standard?
Well, someone must cook it up as a patch, with proper indentation,
based on current tree, add some documentation, and hope it's
considered useful.
I might try next week,
>> 1. Read disk file into RAM
>> 2. Implement custom "mem2env" command to read memory into environment
>> variable, with destination variable as ${bootargs}
I've done the same (on u-boot-1.2.0) to read an upgrade script from a
network file or usb pen. I called the command "setenvram" (bad choice,
> As far as I know CFG_MAX_FLASH_BANKS should be set to 1 always.
> Multiple flash banks in u-boot are not supported.
I have a system with two banks.
u-boot> flinfo
Bank # 1: CFI conformant FLASH (16 x 16) Size: 16 MB in 131 Sectors
Intel Extended command set, Manufacturer ID: 0x89
> If possible, we *want* the preprocessor to remove any code that does
> not apply for a specific configuration. Generating code just bloats
> the memory footprint.
Definitely.
But constant expressions are evaluated at compile time. So the dead
branch (if or else) doesn't generate any object co
> +#if CFG_HZ > 10
Shouldn't this be
if (CFG_HZ > 10)
instead?
It's a constant expression, and the compiler optimizes the conditional
out. Using if() instead of #if ensures that all the code is always parsed,
so the compiler can review it all and signal any problem. Not to ment
> I have another similar board but with the SDRAM as 16MB. I have
> changed the CONFIG_LOAD_ADDR to 0x20f0 but still the mapfile
> shows the text starting at 0x23f0. Can you tell me what are the
> changes I need to make to change the starting location?
The link address is specified in "co
> Hmm... So I must know detailed memory map, and that depends on U-Boot usage,
> right? - the board manual just tells the principle and the end addresses of
> the SDRAM... - maybe the information I am looking for is in the sources of
> U-Boot...
Most likely u-boot is running at 0x23f0.. Us
