Skip to contentSkip to conversation

defconfig for v850, please

DISCUSSION Jan Dittmer 3 participants 8 messages Jul 20, 2005

lore
Share & tools
lore
#0 lore raw

Miles,

while you're at it patching v850 here and there, could you please also provide a resonable defconfig for v850, so that

$ make ARCH=v850 CROSS_COMPILE=... defconfig
$ make ARCH=v850 CROSS_COMPILE=...

works? Then my cross-compile tests at http://l4x.org/k could probably provide somewhat meanigful results for this arch?!

Thanks,

Signature · 1 line
Jan
#1 lore raw

2005/7/20, Jan Dittmer <[email protected]>:

Quoted 2 lines

while you're at it patching v850 here and there, could you please also provide a resonable defconfig for v850, so that

I must admit it's because I've never quite understood how the defconfig stuff works... I'll look into it I guess...

-miles

Signature · 1 line
Do not taunt Happy Fun Ball.
#2 lore raw
Quoted 8 lines · Miles Bader

2005/7/20, Jan Dittmer <[email protected]>:

Quoted 2 lines

while you're at it patching v850 here and there, could you please also provide a resonable defconfig for v850, so that

I must admit it's because I've never quite understood how the defconfig stuff works... I'll look into it I guess...

I think you just need to provide a file called 'defconfig' in arch/v850/

Thanks,

Signature · 1 line
Jan
#3 lore raw

2005/7/20, Jan Dittmer <[email protected]>:

Quoted 5 lines
Quoted 2 lines

I must admit it's because I've never quite understood how the defconfig stuff works... I'll look into it I guess...

I think you just need to provide a file called 'defconfig' in arch/v850/

Hmmm...

Some archs seem to provide defconfigs for various different platforms, which seems nice, and there seems to be some sort of framework for doing this, but ...

-Miles

Signature · 1 line
Do not taunt Happy Fun Ball.
#4 lore raw
Quoted 9 lines · Miles Bader

2005/7/20, Jan Dittmer <[email protected]>:

Quoted 5 lines
Quoted 2 lines

I must admit it's because I've never quite understood how the defconfig stuff works... I'll look into it I guess...

I think you just need to provide a file called 'defconfig' in arch/v850/

Quoted 5 lines

Hmmm...

Some archs seem to provide defconfigs for various different platforms, which seems nice, and there seems to be some sort of framework for doing this, but ...

dropping them in arch/v850/configs/{yourwildplatform}_defconfig seems to be the way most archs do this (ia64, arm). They also provide a common defconfig file in arch/v850/ .

HTH,

Signature · 1 line
Jan
#5 lore raw
In reply to Miles Bader
Quoted 4 lines · Miles Bader

Some archs seem to provide defconfigs for various different platforms, which seems nice, and there seems to be some sort of framework for doing this, but ...

For most of the architectures aimed at embedded systems, having an arch/foo/defconfig makes no sense. The basic "framework" is to have arch/foo/configs and place all of your board-specific defconfigs in there (as boardname_defconfig -- the reason for this is that you get free make targets of the same name which copy the defconfig over, see 'make help').

If you have a particular board that you can assume will be kept reasonably up-to-date, you can set KBUILD_DEFCONFIG in your Makefile to set the default config to use by name, and then you can forego having an arch/foo/defconfig entirely (you can look at sh and some of the other architectures to see this being done).

#6 lore raw
Quoted 9 lines · Paul Mundt
Quoted 4 lines · Miles Bader

Some archs seem to provide defconfigs for various different platforms, which seems nice, and there seems to be some sort of framework for doing this, but ...

For most of the architectures aimed at embedded systems, having an arch/foo/defconfig makes no sense. The basic "framework" is to have

Still, for basic compile testing and testing patches on other architectures it would be nice, when the patch writer can test his/her patch with a simple defconfig, without knowing a common platform for this target arch.
So please include a defconfig with a reasonable common set of CONFIG_* options. It's about testing the core of the architecure not about random driver failures.

Quoted 9 lines

arch/foo/configs and place all of your board-specific defconfigs in there (as boardname_defconfig -- the reason for this is that you get free make targets of the same name which copy the defconfig over, see 'make help').

If you have a particular board that you can assume will be kept reasonably up-to-date, you can set KBUILD_DEFCONFIG in your Makefile to set the default config to use by name, and then you can forego having an arch/foo/defconfig entirely (you can look at sh and some of the other architectures to see this being done).

arm is another one which uses this style, ia64 for example uses configs/* and defconfig. But on arm and sh make defconfig works contrary to v850.

Thanks,

Signature · 1 line
Jan
#7 lore raw
Quoted 4 lines · Jan Dittmer

Still, for basic compile testing and testing patches on other architectures it would be nice, when the patch writer can test his/her patch with a simple defconfig, without knowing a common platform for this target arch.

This is what KBUILD_DEFCONFIG is for. A general purpose defconfig that has no hope of being kept up-to-date is worse than useless.

Quoted 3 lines

arm is another one which uses this style, ia64 for example uses configs/* and defconfig. But on arm and sh make defconfig works contrary to v850.

That's because it looks at KBUILD_DEFCONFIG.. We absolutely do not want to have an arch/foo/defconfig for most of these architectures, and I doubt that v850 is an exception. Note that sh also does not have one.