Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fiona Klute via buildroot <buildroot@buildroot.org>
To: buildroot@cairnwater.com, Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Adding Device Tree Overlays for MIPI-CSI2 Camera and libcamera to a buildroot Build
Date: Wed, 21 May 2025 19:17:55 +0200	[thread overview]
Message-ID: <84ee5308-0c43-4c05-8511-c54870577d33@gmx.de> (raw)
In-Reply-To: <a5a0d49d46a4abc8eaa9a41a4646fd34@cairnwater.com>

Hi Will!

Am 15.05.25 um 18:11 schrieb buildroot@cairnwater.com:
> I see that in acmesystems defconfig :-)
> 
> https://github.com/buildroot/buildroot/blob/master/configs/ 
> acmesystems_acqua_a5_256mb_defconfig
> 
> I hadn't understood that I could add lines to the defonfig file.
> 
> What's the best way for me to keep my changes separate from the 
> underlying defconfig? Should I write a short config file that inherits 
> the defconfig and applies my changes?

The approach I usually use is to create a custom defconfig, and maintain 
that in an external tree (assuming it's a customized one, not a basic 
one that could be contributed to Buildroot).

Usually you shouldn't need to modify the defconfig file by hand, instead 
just use "make nconfig" (or "make menuconfig", etc., whichever you 
prefer) to adjust your config, change BR2_DEFCONFIG to whatever location 
you want, and run "make savedefconfig" to create the defconfig file.

Best regards,
Fiona

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-05-21 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 15:41 [Buildroot] Adding Device Tree Overlays for MIPI-CSI2 Camera and libcamera to a buildroot Build buildroot
2025-05-07 16:41 ` Fiona Klute via buildroot
2025-05-07 18:31   ` buildroot
2025-05-07 20:06     ` Fiona Klute via buildroot
2025-05-08  7:46       ` buildroot
2025-05-14 17:36         ` buildroot
2025-05-14 18:59           ` Edgar Bonet via buildroot
2025-05-15 16:11             ` buildroot
2025-05-21 17:17               ` Fiona Klute via buildroot [this message]
2025-05-21 17:26           ` Fiona Klute via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84ee5308-0c43-4c05-8511-c54870577d33@gmx.de \
    --to=buildroot@buildroot.org \
    --cc=bonet@grenoble.cnrs.fr \
    --cc=buildroot@cairnwater.com \
    --cc=fiona.klute@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox