From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8616] Fail to build for raspberrypi_defconfig with big endian
Date: Thu, 21 Jan 2016 16:55:49 +0000 [thread overview]
Message-ID: <bug-8616-163-eTqMcx1Aa7@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8616-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8616
Gustavo Zacarias <gustavo@zacarias.com.ar> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Gustavo Zacarias <gustavo@zacarias.com.ar> ---
You can't just change endianness arbitrarily and expect that to work.
For starters the pre-compiled rpi-firmware required for the boot process is
only enabled for little-endian, which gives you the error you're seeing because
it's not installed for big-endian.
I don't have much technical detail about the broadcom SOCs used in the rpi1/2
and how open they're to changing endianness, some SOCs require hardware changes
(pin bootstrap), others can be switched in the bootloader, others use fuses and
some can't be changed.
Even if they could be switched in the bootloader for the rpi boards that's a
propietary blob in rpi-firmware, so there's not much you can do.
I'm closing this as invalid.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-01-21 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 14:28 [Buildroot] [Bug 8616] New: Fail to build for raspberrypi_defconfig with big endian bugzilla at busybox.net
2016-01-21 16:55 ` bugzilla at busybox.net [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-8616-163-eTqMcx1Aa7@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