From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: zImage: ensure header in LE format for BE8 kernels
Date: Wed, 18 Jun 2014 11:22:54 -0700 [thread overview]
Message-ID: <53A1D8FE.6030404@codeaurora.org> (raw)
In-Reply-To: <CAGa+x86DfDjQG8gN2-x7Kapt2ipsYt879R4OK6JWGoaT93VVig@mail.gmail.com>
On 06/18/14 11:21, Kevin Hilman wrote:
> On Wed, Jun 18, 2014 at 11:14 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> On 06/18/14 10:55, Kevin Hilman wrote:
>>> All of that to say, with this patch applied, I need a new (and
>>> reliable) way to determine the endianness of a kernel just by looking
>>> at the zImage. Recommendations welcome.
>> Assuming that you have the .config configured to be built into the
>> kernel you could use extract-ikconfig
>>
>> $ ./scripts/extract-ikconfig zImage | grep CONFIG_CPU_ENDIAN_BE8
> Unfortunately, I can't rely on having that built in since I want the
> boot tools to be as generic as possible.
>
>
Yeah ok. Perhaps you can look for the 'setend be' instruction right
after the magic values instead.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-06-18 18:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 16:27 [PATCH] ARM: zImage: ensure header in LE format for BE8 kernels Taras Kondratiuk
2014-04-10 17:03 ` Nicolas Pitre
2014-06-17 14:29 ` Russell King - ARM Linux
2014-06-17 16:07 ` Nicolas Pitre
2014-06-18 17:55 ` Kevin Hilman
2014-06-18 18:14 ` Stephen Boyd
2014-06-18 18:21 ` Kevin Hilman
2014-06-18 18:22 ` Stephen Boyd [this message]
2014-06-18 19:01 ` Kevin Hilman
2014-06-18 21:35 ` Nicolas Pitre
2014-06-19 18:27 ` Kevin Hilman
2014-06-19 20:32 ` Nicolas Pitre
2014-06-19 20:57 ` Kevin Hilman
2014-06-19 21:49 ` Nicolas Pitre
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=53A1D8FE.6030404@codeaurora.org \
--to=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).