Page History

...

• make menuconfig - for configuration changes to buildroot
  • saved to .config
• make linux-menuconfig - for configuration changes to the kernel
  • saved to output/build/linux-<version>/.config
• make busybox-menuconfig - for changes to BusyBox
  • saved to output/build/busybox-<version>/.config

And then subsequently save them (your changes to the config) outside buildroot by running:

• make savedefconfig
  • saved to site/br2-external/configs/<architecture>_defconfig
• make linux-update-defconfig
  • saved to output/build/linux-<version>/defconfig
    • saved to site/config/linux-<version>-common.config ??? when "make" is executed
• cp output/build/busybox-<version>/.config site/config/bb-<version>.config

...

When you run the "save" commands you are saving the config files to the "site" directory where you will later push them to git.  They will be preserved in git so we don't make the same changes for  the next version of buildroot (artifacts).

Under which config (buildroot, linux, busybox) a config option exists isn't always obvious until you find it.

...