Messages in this thread | | | Date | Tue, 9 Sep 2003 21:29:18 +0200 | From | Sam Ravnborg <> | Subject | Multiple configuration support |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |