From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/2] km: adapt defines and variables for new memory layout
Date: Thu, 22 Oct 2020 20:29:28 -0400 [thread overview]
Message-ID: <20201023002928.GS14816@bill-the-cat> (raw)
In-Reply-To: <20201009152133.27389-1-holger.brunck@hitachi-powergrids.com>
On Fri, Oct 09, 2020 at 05:21:32PM +0200, Holger Brunck wrote:
> Due to increasing kernel image sizes we get problems when decompressing
> the kernel image. To fix this we need to change the addresses where we
> load and where we extract the kernel. Also we need to adapt the address
> where to load the CRAMFS image and where to load the DTB file.
> While at it also harmonize all boards for PPC and ARM to have the
> same values. Also we add a new variable "env_version", so that the
> userspace is able to detect if this is a u-boot binary with updated
> values or not.
>
> CC: Valentin Longchamp <valentin.longchamp@hitachi-powergrids.com>
> CC: Heiko Schocher <hs@denx.de>
> CC: Tom Rini <trini@konsulko.com>
> Signed-off-by: Holger Brunck <holger.brunck@hitachi-powergrids.com>
> Reviewed-by: Heiko Schocher <hs@denx.de>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201022/5060cfdf/attachment.sig>
prev parent reply other threads:[~2020-10-23 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 15:21 [PATCH v2 1/2] km: adapt defines and variables for new memory layout Holger Brunck
2020-10-09 15:21 ` [PATCH v2 2/2] km/common: change ubicopy variable Holger Brunck
2020-10-12 4:08 ` Heiko Schocher
2020-10-23 0:29 ` Tom Rini
2020-10-12 4:07 ` [PATCH v2 1/2] km: adapt defines and variables for new memory layout Heiko Schocher
2020-10-23 0:29 ` Tom Rini [this message]
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=20201023002928.GS14816@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