From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15196] New: Setting BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE does not work
Date: Wed, 21 Dec 2022 10:00:35 +0000 [thread overview]
Message-ID: <bug-15196-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15196
Bug ID: 15196
Summary: Setting BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE does not
work
Product: buildroot
Version: 2022.08.3
Hardware: Other
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: mats.webjorn@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
.config in buildroot root has been configured with
BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE="xxx/boot/config.txt"
administrator@zzzz:~/project/buildroot/xxx/boot $ ls -l
total 8
-rw-rw-r-- 1 administrator administrator 1612 Dec 19 22:44 config.txt
But the boot partition in the image doesn't contain my version of config.txt
What is seen in build log is
INFO: vfat(boot.vfat): adding file 'rpi-firmware/config.txt' as
'rpi-firmware/config.txt' ...
INFO: vfat(boot.vfat): cmd: "MTOOLS_SKIP_CHECK=1 mcopy -sp -i
'/home/administrator/project/buildroot/output/images/boot.vfat'
'/home/administrator/project/buildroot/output/images/rpi-firmware/config.txt'
'::'" (stderr):
Is there any other setting that needs to done?
--
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
next reply other threads:[~2022-12-21 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:00 bugzilla [this message]
2022-12-21 10:01 ` [Buildroot] [Bug 15196] Setting BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE does not work bugzilla
2022-12-21 11:25 ` bugzilla
2022-12-21 13:10 ` bugzilla
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@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.