From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARMv8: add optional Linux kernel image header
Date: Wed, 3 Jan 2018 08:45:26 -0500 [thread overview]
Message-ID: <20180103134526.GS31350@bill-the-cat> (raw)
In-Reply-To: <20180102235422.2866-1-swarren@wwwdotorg.org>
On Tue, Jan 02, 2018 at 04:54:21PM -0700, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Allow placing a Linux kernel image header at the start of the U-Boot
> binary. This is useful since the image header reports the amount of memory
> (BSS and similar) that U-Boot needs to use, but that isn't part of the
> binary size. This can be used by the code that loads U-Boot into memory to
> determine where to load U-Boot, based on other users of memory.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> This series relies (at the very least for diff context) on the previous
> series I sent Dec 19: ARM: tegra: don't use CONFIG_SPL_TEXT_BASE when no
> SPL ... ARM: tegra: use CONFIG_SYS_INIT_SP_BSS_OFFSET.
Neat. Are the Linux folks encouraging other projects to re-use this
header? Is there somewhere we can point to as reference for the format
for the Kconfig help as well, not just the text? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180103/fd04853e/attachment.sig>
next prev parent reply other threads:[~2018-01-03 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 23:54 [U-Boot] [PATCH 1/2] ARMv8: add optional Linux kernel image header Stephen Warren
2018-01-02 23:54 ` [U-Boot] [PATCH 2/2] ARM: tegra: use LINUX_KERNEL_IMAGE_HEADER Stephen Warren
2018-01-08 4:50 ` Simon Glass
2018-01-08 18:23 ` Stephen Warren
2018-01-03 13:45 ` Tom Rini [this message]
2018-01-03 17:42 ` [U-Boot] [PATCH 1/2] ARMv8: add optional Linux kernel image header Stephen Warren
2018-01-03 17:56 ` Tom Rini
2018-01-03 21:31 ` Stephen Warren
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=20180103134526.GS31350@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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