From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org,
Ezequiel Garcia <ezequiel.garcia@imgtec.com>,
James Hartley <james.hartley@imgtec.com>,
James Hogan <james.hogan@imgtec.com>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address
Date: Tue, 24 Feb 2015 09:15:12 +0100 [thread overview]
Message-ID: <7814815.Q6KYv1fjo1@wuerfel> (raw)
In-Reply-To: <1424741507-8882-3-git-send-email-abrestic@chromium.org>
On Monday 23 February 2015 17:31:44 Andrew Bresticker wrote:
> Platforms which use raw zboot images may need to link the image at
> a fixed address if there is no other way to communicate the load
> address to the bootloader. Allow the per-platform Kbuild files
> to specify an optional zboot image load address (zload-y) and fall
> back to calc_vmlinuz_load_addr if unset.
>
> Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
No objections to the patch, but have you considered doing the
same thing as ARM's AUTO_ZRELADDR, where we calculate the
address at runtime from the entry point?
I assume this is the same kind of address you are talking
about here; if not, nevermind.
Arnd
next prev parent reply other threads:[~2015-02-24 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 1:31 [PATCH 0/5] MIPS: Initial IMG Pistachio SoC support Andrew Bresticker
2015-02-24 1:31 ` [PATCH 1/5] MIPS: Create a common <asm/mach-generic/war.h> Andrew Bresticker
2015-02-24 1:31 ` [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address Andrew Bresticker
2015-02-24 8:15 ` Arnd Bergmann [this message]
2015-02-24 21:39 ` Andrew Bresticker
[not found] ` <CAL1qeaHSErgc=W4mGhDAm7cu_J4wrOik27joB0Rd-2P7dk=QuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-24 22:42 ` Ralf Baechle
2015-02-24 1:31 ` [PATCH 3/5] MIPS: Document Pistachio boot protocol and device-tree bindings Andrew Bresticker
2015-02-24 1:31 ` [PATCH 4/5] MIPS: Add support for the IMG Pistachio SoC Andrew Bresticker
2015-02-24 1:31 ` [PATCH 5/5] MIPS: pistachio: Add an initial defconfig Andrew Bresticker
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=7814815.Q6KYv1fjo1@wuerfel \
--to=arnd@arndb.de \
--cc=abrestic@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@imgtec.com \
--cc=james.hartley@imgtec.com \
--cc=james.hogan@imgtec.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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