2 Dec
2009
2 Dec
'09
6:07 p.m.
apgmoorthy wrote:
I felt moving these macros "include/linux/mtd/onenand.h" will be ideal in this scenario.
Are they going to be the same on all boards? We let the board determine the environment location for other types of storage.
How about just using CONFIG_ENV_ADDR/CONFIG_ENV_SIZE? On boards that must dynamically support multiple possibilities, define it as an expression that returns the right thing.
-Scot