bloated defconfigs

[Andreas Kemnade <andreas@kemnade.info>]

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

Hi,

I just stumbled upon our defconfigs.

andi@aktux:~/gta04/gta04-kernel$ ls -l arch/arm/configs/ -Sr | tail -n
10 -rw-r--r-- 1 andi andi   9524 Apr  7 14:53 imote2_defconfig
-rw-r--r-- 1 andi andi   9985 Jul 28 13:34 imx_v6_v7_defconfig
-rw-r--r-- 1 andi andi  10118 Apr  7 14:53 ezx_defconfig
-rw-r--r-- 1 andi andi  10665 Apr  7 14:53 s3c2410_defconfig
-rw-r--r-- 1 andi andi  13161 May 29 18:14 omap2plus_defconfig
-rw-r--r-- 1 andi andi  17834 May 29 18:14 pxa_defconfig
-rw-r--r-- 1 andi andi  24624 Jul 28 13:34 multi_v7_defconfig
-rw-r--r-- 1 andi andi 157222 Jul 28 13:34 letux_udoo_defconfig
-rw-r--r-- 1 andi andi 157271 Jul 28 13:34 letux_lpae_defconfig
-rw-r--r-- 1 andi andi 157352 Jul 28 13:34 letux_defconfig


So we are bloated somehow. So I am wondering how these defconfigs are created.
AFAIK the tool is

make ARCH=arm CROSS_COMPILE=... savedefconfig

the file can then be used as a defconfig. I just did it and copied it over to
.config and used
make ARCH=arm CROSS_COMPILE=... olddefconfig

The result is the same. But the defconfig created by savedefconfig is only 20KB.
Well, what is the advantage? We have a better overview where we have
non-default values.

Regards,
Andreas

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]