Dear Bo Shen, In message <1376230503-25331-1-git-send-email-voice.s...@gmail.com> you wrote: > when CONFIG_ENV_IS_NOWHERE is enabled, it is still need to define > CONFIG_ENV_SIZE. So, add a default size (1024 Bytes) to avoid > compile error if not define CONFIG_ENV_SIZE
I don;t understand the rationale for this patch. In which way is the environment seize for the CONFIG_ENV_IS_NOWHERE case different from any other cases? For these, we do not define a default either, so why should we handle this case differently? In any cse, the needed environment seize if a pretty board specific thing, and I think it makes sense to let the user define it. 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: w...@denx.de Anyone who isn't confused here doesn't really know what's going on. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
