This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

linux defconfig file

Guru 20755 points

Hello,

I would like to ask a general question about defconfig file.

On doing 

make xxx_defconfig , I get a new .config file. I assumed it is the same as xxx_defconfig, but on viewing it I see differences.
for example, I modified the
xxx_defconfig as following:

old:
CONFIG_OMAP_MUX=y
new:
# CONFIG_OMAP_MUX=y
but after doing 
make xxx_defconfig , I see in .config :

 CONFIG_OMAP_MUX=y

Does anybody know why is that ?

Thanks

Ran

  • Hi Ran,

    Are you editing the .config manually ?

    You should modify the .config through "make menuconfig".

    # CONFIG_OMAP_MUX=y ---> OMAP muxing support disabled

    but It seems to be someone edited manually, if we changed the "OMAP MUX" support through "make menuconfig" then you might have seen like below.

    # CONFIG_OMAP_MUX is not set ---> OMAP muxing support disabled

    CONFIG_OMAP_MUX=y ---> OMAP muxing support enabled

  • Hi Titusrathinaraj Stalin,

     

    I tried to manually change the defconfig file with #CONFIG_OMAP_MUX (inside remark), and expected that after doing make ti8148_evm_defconfig, I will see in .config the same, but it did not happen. Only if I change through make mecnuconfig it is OK.

    But why does it not do simple copy after editing the defconfig file, and doing make xxx_defconfig ?

    Thanks,

    Ran

  • Hi Ran,

    As I said earlier, you should not edit the .config file manually.

    If you want some "defconfig" with "OMAP MUX" support then create ".config" with that support and rename to "ti8148_evm_defconfig,"

    cp -rf .config arch/arm/configs/ti8148_evm_defconfig


    Got it !