On 07/13/2010 03:43 AM, Stephen Rothwell wrote: > After this change, doing a "make xxx_defconfig" will check first for > a file called arch/<arch>/configs/Kconfig.xxx and use that to generate > the .config (effectively starting from an allnoconfig). If that file > doesn't exist, it will use arch/<ARCH>/configs/xxx_defconfig as now. > > Signed-off-by: Stephen Rothwell <s...@canb.auug.org.au> > --- > scripts/kconfig/Makefile | 14 +++++++++++++- > 1 files changed, 13 insertions(+), 1 deletions(-) > > Hi Linus, > > Is this more the direction you want to take? > > There are still 2 main problems with is approach: > > - there are some config options that are globally and > unconditionally enabled that some platforms may not want. The only way > currently to turn them off is to reproduce the config entry with the > different default. I am not sure if we need a wa to turn them off or to > just change them to being neede to be selected by those that do want them. > - we have no way to select options that are neither bool or > tristate to suitable values. Again the only way to do that currently is > to reproduce the config entry with a different default value.
Hi Stephen, how are these Kconfig.xxx files going look like? A list of 'select FOO' and 'include "Kconfig.other"' statements? What about adding support for an include statement to the .config file format and using that in the defconfigs instead? The VARIABLE=VALUE grammar seems much more suitable for this than the kconfig language. Michal _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
