Reuse my own kernel configuration file

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi,
I wish to verify how to correctly create and reload my own kernel config file each time I wish to reconfigure and build the kernel.

so far:

  1. make ARCH=arm64 O=$WORKSPACE_PATH/Out tegra_defconfig

  2. make ARCH=arm64 O=$WORKSPACE_PATH/Out menuconfig

  3. modifying configuration and save as new_config.
    the file is being saved as $WORKSPACE_PATH/Out/new_config

now, next time I wish to reconfigure the kernel before build with my new_config, what do I do?

skip (1) and use (2) with new_config as argument?

in addition, how do i make sure my new_config file will be used and not some old .config file wile rebuilding the kernel?

Thanks

3

Hi,

I think you just run Step 3 next time you want to re-build the kernel.
I’m not sure what you get confused with.

4

Thank you for your answer. I’ll try to elaborate:

On step 2, the graphical menuconfig app is opened with some default configuration.

I wish to open the menuconfig app again, “continue where i left” and not start again from the defaults values before i made my changes.

5

I don’t feel like that’s supported in Linux kernel.
Contents of menuconfig is determined by /arch/$(CPU architecture being used)/Kconfig, so it’d always show the same thing each time you run it.

6

But when I execute the following command:

make ARCH=arm64 O=$WORKSPACE_PATH/Out tegra_defconfig

it somehow load some default configuration each time I’ll open menuconfig.

So my logic says I need to create and update my own version of tegra_defconfig?
that way I’ll execute

make ARCH=arm64 O=$WORKSPACE_PATH/Out tegra_defconfig_latest
make ARCH=arm64 O=$WORKSPACE_PATH/Out menuconfig

and my recent values will be restored

7

Oh Yes, I think you are right here.
Populate you own tegra_defconfig then run these:

8

thanks.
I used make savedefconfig

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.