Skip to contentSkip to conversation

Multiple configuration support

DISCUSSION Sam Ravnborg 2 participants 3 messages Sep 9, 2003 – Sep 10, 2003

lore
Share & tools
lore
#0 lore raw

Hi Roman.

Russell pointed out to me in private mail that the current way to select individual configurations are broken with my latest changes, where I moved *config targets to scripts/kconfig/Makefile. The problem is that they use the target filename_config to select the individual configuration (see arch/arm/Makefile).

This brought up an old idea I have had for some time. With the current kconfig it should be doable to have something like the following scheme:
arch/$(ARCH)/defconfig <= As we know it
arch/$(ARCH)/configs/boardconfig

boardconfig should be very simple, only including delta to the default configuration.
So boardconfig would only enable those drivers specific for that board and other relevant config information. For example defconfig selected the Opetron CPU, then boardconfig could change this to an 486 CPU.

Example boardconfig file:
CONFIG_M486=y

I cannot see how this would work with choice etc., would that be a problem?

This scheme would make it less cumbersome to maintain the dozen of different configuration files as included by arm, ppc, ppc64 today.

Comments to that approach?

I tried to look into this, but was stuck in conf_read(). When the file has been opened conf_read() set all symbols back to default values, so I could not call it twice.
And I didn't want to fiddle to much with the public interface of kconfig for now.

Sam

#1 lore raw
Quoted 2 lines · Sam Ravnborg

boardconfig should be very simple, only including delta to the default configuration.

The delta is going to be fairly large for ARM - it doesn't make sense to have a default core configuration and per-board deltas.

Signature · 5 lines
Russell King ([email protected])	http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
  2.6 ARM Linux   - http://www.arm.linux.org.uk/
  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
  2.6 Serial core
#2 lore raw
Quoted 6 lines · Russell King
Quoted 2 lines · Sam Ravnborg

boardconfig should be very simple, only including delta to the default configuration.

The delta is going to be fairly large for ARM - it doesn't make sense to have a default core configuration and per-board deltas.

OK.
I already dropped my current implementation (got it working by patching a bit in kconfig, but realised the same can be achived by preprocessing the config files).
So to make it clear - the above functionality is NOT implemented in the patchset I just sent to Linus.

Sam