From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 boot requirements
Date: Wed, 2 Dec 2015 10:26:55 +0000 [thread overview]
Message-ID: <20151202102655.GA21365@leverpostej> (raw)
In-Reply-To: <565E1A8E.8000506@codeaurora.org>
On Tue, Dec 01, 2015 at 05:09:18PM -0500, Christopher Covington wrote:
> On 12/01/2015 06:52 AM, Ard Biesheuvel wrote:
> > However, I strongly feel that the Image header should remain the
> > authoritative source of information regarding the nature (big/little
> > endian, page size) and the static footprint of the Image.
>
> I find `readelf -a | less` quite handy. Is there anything comparable for
> the AArch64 Image format?
Not that I am aware of. These days I just use od or hexedit, and parse
the header manually.
It's documented, so it would be possible to write one.
> Please forgive my ignorance, but is the EFI stub another possible source
> for sort of information?
Not really. The PE/COFF header for the EFI stub realistically only tells
you wether or not the kernel has an EFI stub. It shouldn't be used to
derive information about the kernel itself.
Thanks,
Mark.
next prev parent reply other threads:[~2015-12-02 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 1:45 arm64 boot requirements Carl van Schaik
2015-12-01 11:02 ` Mark Rutland
2015-12-01 11:52 ` Ard Biesheuvel
2015-12-01 22:09 ` Christopher Covington
2015-12-02 10:26 ` Mark Rutland [this message]
2015-12-02 13:46 ` Carl van Schaik
2015-12-03 12:24 ` Mark Rutland
2015-12-01 12:50 ` Pratyush Anand
2015-12-02 19:03 ` Geoff Levand
2015-12-03 12:29 ` Mark Rutland
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=20151202102655.GA21365@leverpostej \
--to=mark.rutland@arm.com \
--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