From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Big endian working?
Date: Tue, 08 Apr 2014 21:03:24 +0200 [thread overview]
Message-ID: <12950765.TpxjkTx5NP@wuerfel> (raw)
In-Reply-To: <5343BDEE.4010005@linaro.org>
On Tuesday 08 April 2014 12:14:22 Taras Kondratiuk wrote:
> On 04/08/2014 10:54 AM, Thomas Petazzoni wrote:
> > Hello Taras,
> >
> > I'm currently trying to get ARM BE to work on Armada XP. I'm pretty
> > sure it used to work on 3.13, but now I'm testing 3.13 and 3.14 and it
> > doesn't boot here (it hangs even before "Uncompressing kernel...",
> > apparently while relocating the kernel image before decompression).
> >
> > Ben Dooks told me that the ARM BE kernel works for you. Can you confirm
> > which kernel version you're using, and if you've applied any patch?
> > Also, can you confirm which toolchain and toolchain version you're
> > using?
>
> Hi Tom
>
> To boot BE kernel from LE u-boot I'm using a few patches on top of
> upstream kernel.
>
> git://git.linaro.org/people/taras.kondratiuk/linux.git arm-be-boot-le
>
> ----------------------------------------------------------------
> Ben Dooks (1):
> ARM: add CPU_BE8_BOOT_LE configuration
>
> Nico Pitre (1):
> ARM: ensure loader information in LE format for BE kernels
Sorry for lacking the history on this patch set, but why would
you ever want to have this as a compile-time conditional?
Did anyone really put a u-boot on shipping hardware that expects
the headers in big-endian format?
Arnd
next prev parent reply other threads:[~2014-04-08 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 7:54 Big endian working? Thomas Petazzoni
2014-04-08 9:14 ` Taras Kondratiuk
2014-04-08 19:03 ` Arnd Bergmann [this message]
2014-04-09 3:44 ` Nicolas Pitre
2014-04-09 4:46 ` Victor Kamensky
2014-04-09 5:30 ` Thomas Petazzoni
2014-04-09 7:09 ` Arnd Bergmann
2014-04-09 9:04 ` Taras Kondratiuk
2014-04-09 9:38 ` Arnd Bergmann
2014-04-09 16:17 ` Victor Kamensky
2014-04-09 16:35 ` Marc Zyngier
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=12950765.TpxjkTx5NP@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox