[Buildroot] [Bug 13026] New: rpi-firmware: must not rename start files

[Buildroot] [Bug 13026] New: rpi-firmware: must not rename start files

[bugzilla at busybox.net]

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.

[Buildroot] [Bug 13026] rpi-firmware: must not rename start files

[bugzilla at busybox.net]

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

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
Fixed by
https://git.buildroot.org/buildroot/commit/?id=72bf704f0313b314bc52dbebfd2b2e62d4fed5b3,
thanks

-- 
You are receiving this mail because:
You are on the CC list for the bug.