bloated defconfigs
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
Quoted 22 lines · Andreas Kemnade
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(quoted diff) +0
-9-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_defconfigSo we are bloated somehow. So I am wondering how these defconfigs are created. AFAIK the tool is
make ARCH=arm CROSS_COMPILE=... savedefconfig
Quoted 7 lines
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=... olddefconfigThe 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.
So, why not to send patches?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Hi,
Quoted 27 lines · On Sat, 28 Jul 2018 16:01:41 +0300 Andy Shevchenko <[email protected]>…
Quoted 26 lines · Andreas Kemnade
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(quoted diff) +0
-9-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_defconfigSo 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
Quoted 6 lines
Quoted 3 lines
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.
So, why not to send patches?
sorry for the noise, wrong list, these bloated letux*defconfigs are not mainline.
Regards,
Andreas