All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15196] Setting BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE does not work
Date: Wed, 21 Dec 2022 13:10:16 +0000	[thread overview]
Message-ID: <bug-15196-163-jh0TSYfj8V@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15196-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15196

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998@free.fr
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Mats, All,

> output/images/rpi-firmware/config.txt hasn't updated with
> content from xxx/boot/config.txt

config.txt is instaleld by the rpi-firmware package, so when you change it
(or change BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE to point to another file),
then you need to instruct Buildroot to reinstall the package:

    $ make rpi-firmware-reinstall

Otherwise, when changing the configuration (like changing
BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE is), Buildroot only guarantees that
it is entorely taken into account on a full rebuild:

    $ make clean; make

See the manual:

    https://buildroot.org/downloads/manual/manual.html#_full_rebuild

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-12-21 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 10:00 [Buildroot] [Bug 15196] New: Setting BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE does not work bugzilla
2022-12-21 10:01 ` [Buildroot] [Bug 15196] " bugzilla
2022-12-21 11:25 ` bugzilla
2022-12-21 13:10 ` bugzilla [this message]

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=bug-15196-163-jh0TSYfj8V@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.