On 01:22 Sun 14 Jun , Wolfgang Denk wrote:
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090613191845.GM25406@game.jcrosoft.org you wrote:
NAK.
The ARM mach ID thing is evil, and shall not spread into the U-Boot code - especially since it is ARM only and not usable for other architectures.
there is nothing to do with the ARM mach ID here it just the board and arch
So "CONFIG_MACH_xxx for machine" is not an ARM mach-id?
no the machine id is MACH_TYPE_XXXX
CONFIG_MACH_XXX is the config for the board also call machine on ARM
as example on SH the boards configs are
CONFIG_SH_XXXX as
CONFIG_SH_SH7763RDP or CONFIG_SH_SH7785LCR
for avr32 it's CONFIG_BOARD_XXXXX as CONFIG_BOARD_ATNGW100 CONFIG_BOARD_ATSTK1000
So who the hell does define that if it is not include/asm-arm/mach-types.h ???
the Kconfig and for all arch
CONFIGs and as I said in the other e-mail it's not ARM only you can do the same for all arch as it also based on Kconfig linux kernel files
Introduce mach-id's for all architectures? What have you been smoking today? Go away!
Please read carefully, I will not repeat it: we will not introduce CONFIG_MACH_xxx in U-Boot.
I never said to use it for all arch just to use the same scheme as each linux arch
so please reconsider it
Best Regards, J.