From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix microblize little endian toolchain
Date: Wed, 19 Mar 2014 10:02:07 -0300 [thread overview]
Message-ID: <5329954F.7060701@zacarias.com.ar> (raw)
In-Reply-To: <1395230465-4421-1-git-send-email-xvikto03@stud.fit.vutbr.cz>
On 03/19/2014 09:01 AM, Jan Viktorin wrote:
> From: Jan Drazil <xdrazi00@stud.fit.vutbr.cz>
>
> Buildroot toolchain creates big endian binaries instead of little endian
> ones for microblaze architecture. The reason is wrong BR2_ARCH string.
> KERNEL_ARCH must contain microblaze in both cases.
>
> Signed-off-by: Jan Drazil <xdrazi00@stud.fit.vutbr.cz>
> Signed-off-by: Jan Viktorin <xvikto03@stud.fit.vutbr.cz>
Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
The qemu_microblazeel_mmu_defconfig now starts the kernel (before it was
a big failure). Still not great since OOM killer strikes before the
login prompt.
Regards.
next prev parent reply other threads:[~2014-03-19 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 12:01 [Buildroot] [PATCH 1/1] Fix microblize little endian toolchain Jan Viktorin
2014-03-19 13:02 ` Gustavo Zacarias [this message]
2014-03-19 13:53 ` Jan Viktorin
2014-03-20 15:47 ` Peter Korsgaard
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=5329954F.7060701@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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