Skip to contentSkip to conversation

ARM config scheme for board and machine update

U-Boot Jean-Christophe PLAGNIOL-VILLARD 2 participants 4 messages Jun 13, 2009

lore
Share & tools
lore
#0 lore raw

Hi,

Currently boards and arch define there own CONFIG_IXP or CONFIG_VCMA9 where they are also have a define in the mach-types.h

so now to simplify linux code share and reduce duplicate define we switch to the linux style (please check the mach-types.h for it)

CONFIG_ARCH_xxx for arch
and
CONFIG_MACH_xxx for machine

for board and arch that are send precedently to this announce will not have to switch to be ack but it will nice to do it. We will switch the current one step by step

For other arch and board it will be mandotory

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

Best Regards,
J.

#1 lore raw

Dear Jean-Christophe PLAGNIOL-VILLARD,

Quoted 11 lines · In message <[email protected]> you wrote:

Currently boards and arch define there own CONFIG_IXP or CONFIG_VCMA9 where they are also have a define in the mach-types.h

so now to simplify linux code share and reduce duplicate define we switch to the linux style (please check the mach-types.h for it)

CONFIG_ARCH_xxx for arch
and
CONFIG_MACH_xxx for machine

Quoted 8 lines

for board and arch that are send precedently to this announce will not have to switch to be ack but it will nice to do it. We will switch the current one step by step

For other arch and board it will be mandotory

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.

Best regards,

Wolfgang Denk

Signature · 4 lines
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: wd at denx.de
Don't have a battle of wits with an unarmed opponent.
#2 lore raw
Quoted 20 lines · Wolfgang Denk

Dear Jean-Christophe PLAGNIOL-VILLARD,

Quoted 17 lines · In message <[email protected]> you wrote:

Currently boards and arch define there own CONFIG_IXP or CONFIG_VCMA9 where they are also have a define in the mach-types.h

so now to simplify linux code share and reduce duplicate define we switch to the linux style (please check the mach-types.h for it)

CONFIG_ARCH_xxx for arch
and
CONFIG_MACH_xxx for machine

for board and arch that are send precedently to this announce will not have to switch to be ack but it will nice to do it. We will switch the current one step by step

For other arch and board it will be mandotory

Quoted 8 lines
Quoted 2 lines

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.
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

Best Regards,
J.

#3 lore raw

Dear Jean-Christophe PLAGNIOL-VILLARD,

Quoted 11 lines · In message <[email protected]> you wrote:
Quoted 9 lines
Quoted 3 lines

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.

Quoted 3 lines

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

Signature · 4 lines
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: wd at denx.de
2000 pounds of chinese soup                               = 1 Won Ton