
17 Jul
2014
17 Jul
'14
2:47 p.m.
Dear Valentin,
In message 1405599840-11984-1-git-send-email-valentin.longchamp@keymile.com you wrote:
When u-boot initializes the RAM (early in boot) it looks for the "pram" env variable to know which is area it cannot use.
At this early boot stage, the "pram" env variable is not avaible yet since it gets computed in set_km_env that gets called AFTER the RAM initialization. If the "pram" env variable is not found, the default CONFIG_PRAM value is used.
Note that I am not objecting against this patch, but I highly recommend to fix your board - RAM initialization is actually pretty late in the init sequence, and you should have a valid envionment long before.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
God may be subtle, but He isn't plain mean. - Albert Einstein