From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Wed, 29 Jul 2015 10:20:38 +0100 [thread overview]
Message-ID: <1438161638.3129.4.camel@linaro.org> (raw)
In-Reply-To: <1438093961-15536-1-git-send-email-msalter@redhat.com>
On Tue, 2015-07-28 at 10:32 -0400, Mark Salter wrote:
> When booting an arm64 kernel w/initrd using UEFI/grub, use of mem= will likely
> cut off part or all of the initrd. This leaves it outside the kernel linear
> map which leads to failure when unpacking.
Have we got a similar issue for the device-tree blob?
--
Tixy
next prev parent reply other threads:[~2015-07-29 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 14:32 [PATCH 0/2] arm64: support initrd outside of mapped RAM Mark Salter
2015-07-28 14:32 ` [PATCH 1/2] mm: add utility for early copy from unmapped ram Mark Salter
2015-07-28 14:32 ` [PATCH 2/2] arm64: support initrd outside kernel linear map Mark Salter
2015-07-28 14:59 ` [PATCH 0/2] arm64: support initrd outside of mapped RAM Mark Rutland
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:14 ` Mark Rutland
2015-07-29 9:20 ` Jon Medhurst (Tixy) [this message]
2015-07-29 9:25 ` 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=1438161638.3129.4.camel@linaro.org \
--to=tixy@linaro.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).