Dear Masahiro, In message <[email protected]> you wrote: > > > Finally, I don't see what your replacement code would be to create the > > set of environment settigns - and I think these are needed, as some > > user defined scripts are processing these? > > The user who needs such environment setting can > add them by using CONFIG_EXTRA_ENV_SETTINGS. > > For example, > > #define CONFIG_EXTRA_ENV_SETTINGS \ > "arch=arm\0" \ > "cpu=armv7\0" \ > "soc=tegra20\0" > > I am not sure this is acceptable.
Neither am I. What I can see is that this is less flexible - as is, we can easily derive these names from the make target name. Your implementation would either be static, or require #ifdefs ? 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: [email protected] If you want strict real-time behavior, run in the real time schedu- ling class. But there are no seatbelts or airbags; main(){for(;;);} can hard hang your system. -- Bart Smaalders _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
