Skip to content

utils: replace generate-defconfig with new update-defconfig - #1691

Merged
rical merged 1 commit into
mainfrom
new-update-defconfig-tool
Oct 7, 2026
Merged

rical merged 1 commit into
mainfrom
new-update-defconfig-tool

Conversation

@rical

@rical rical commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Description

This new tool can be used to interactivly update spin defconfigs. Using the tool, the spin gets a copy of the current infix defconfig in foo_defconfig.base. Running a tool then asks the user what to do with any new config options that has appeared in Infix since the last update. They are also compared to the old spin configs for reference.

Here's a prompt example:

BR2_PACKAGE_NOVARQ_TACTICAL_1000 - Novarq Tactical 1000 (Laguna)
          ours: n  (configs/dcp_sc_28p_defconfig)
  old upstream: n  (configs/dcp_sc_28p_defconfig.base)
  new upstream: y  (infix/configs/aarch64_defconfig)
Use new upstream? [Y/n]

The user can then decide what to do with it. It cal be called with -y to auto select what upstream has done. Mainly for non interactive test runs.

Here's a caller example (Spin makefile):
@$(sync) infix/configs/aarch64_defconfig configs/dcp_sc_28p_defconfig

Checklist

Tick relevant boxes, this PR is-a or has-a:

  • Bugfix
    • Regression tests
    • ChangeLog updates (for next release)
  • Feature
    • YANG model change => revision updated?
    • Regression tests added?
    • ChangeLog updates (for next release)
    • Documentation added?
  • Test changes
    • Checked in changed Readme.adoc (make test-spec)
    • Added new test to group Readme.adoc and yaml file
  • Code style update (formatting, renaming)
  • Refactoring (please detail in commit messages)
  • Build related changes
  • Documentation content changes
    • ChangeLog updated (for major changes)
  • Other (please describe):

This new tool can be used to interactivly update spin defconfigs.
Using the tool, the spin gets a copy of the current infix defconfig
in foo_defconfig.base. Running a tool then asks the user what to
do with any new config options that has appeared in Infix since
the last update. They are also compared to the old spin configs
for reference.

Here's a prompt example:

BR2_PACKAGE_NOVARQ_TACTICAL_1000 - Novarq Tactical 1000 (Laguna)
          ours: n  (configs/dcp_sc_28p_defconfig)
  old upstream: n  (configs/dcp_sc_28p_defconfig.base)
  new upstream: y  (infix/configs/aarch64_defconfig)
Use new upstream? [Y/n]

The user can then decide what to do with it. It cal be called
with -y to auto select what upstream has done. Mainly for non
interactive test runs.

Here's a caller example (Spin makefile):
@$(sync) infix/configs/aarch64_defconfig configs/dcp_sc_28p_defconfig

Signed-off-by: Richard Alpe <richard@bit42.se>

@mattiaswal mattiaswal left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really cool 🔥

@rical
rical merged commit c36333b into main Oct 7, 2026
9 checks passed
@rical
rical deleted the new-update-defconfig-tool branch October 7, 2026 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants