From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13026] New: rpi-firmware: must not rename start files
Date: Wed, 24 Jun 2020 10:04:37 +0000 [thread overview]
Message-ID: <bug-13026-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13026
Bug ID: 13026
Summary: rpi-firmware: must not rename start files
Product: buildroot
Version: 2020.05
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: sveyret at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
When booting, a Raspberry Pi will load the appropriate start files, depending
on the provided configuration. For example, if the config.txt file contains:
gpu_mem=16
the board will automatically load the cut-down startup files (start_cd.elf and
fixup_cd.dat on non-Rpi4). Unfortunately, even when the appropriate version is
selected in the configuration menu (in this example,
BR2_PACKAGE_RPI_FIRMWARE_BOOT="_cd") if the rpi-firmware makefile takes the
good files, it renames them to non-qualified, i.e. start.elf and fixup.dat. But
as these are not the files searched by the Raspberry Pi, the board will not
start.
I will provide a patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-24 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 10:04 bugzilla at busybox.net [this message]
2020-07-25 7:27 ` [Buildroot] [Bug 13026] rpi-firmware: must not rename start files bugzilla at busybox.net
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-13026-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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