Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090613191644.GL25406@game.jcrosoft.org you wrote:
The Kconfig support will be send with in days and it will be also mandatory to have switch to it before be include in it's Kconfig files
How is this supposed to work with non-ARM architectures?
I don't want to see ARM-only code in U-Boot. If we change the board configuration etc., then please in a way that works for all boards and architectures.
I want to have this sync to simplify it. This can be extended to the all boards if you want.
By adapting the mach-id to all other architectures?
Only over my dead body.
For arm all the board and arch config is defined in the mach-types.h so I use it as reference but for other arch the idea can be the same and based if you prefer in the Kconfig linux files
I prefer that we do not use the mach-id for anything unless it is absolutely impossible to avoid it for compatibility with Linux.
Best regards,
Wolfgang Denk