From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 06/10] arm64: efi: add EFI stub
Date: Wed, 8 Feb 2017 10:35:02 -0600 [thread overview]
Message-ID: <73a460e5-98f5-86c2-142f-a9a084ee0203@codeaurora.org> (raw)
In-Reply-To: <E4BDBC23-A96A-4D84-B7EE-B7967D4E4DDD@linaro.org>
On 02/08/2017 10:29 AM, Ard Biesheuvel wrote:
>>> >> + status = handle_cmdline_files(sys_table, image, cmdline_ptr,
>>> >> + "initrd=", dram_base + SZ_512M,
>>> >> + (unsigned long *)&initrd_addr,
>>> >> + (unsigned long *)&initrd_size);
>> >
>> > So I know this patch is almost three years old, but why is there a
>> > 512M limit on the initrd size?
>> >
> How do you reckon this constitutes a limit?
handle_cmdline_files() calls efi_high_alloc() with that limit. I'm still
trying to understand all the details myself, but apparently our firmware and
initrd need to fit within the first 512MB because of dram_base + SZ_512M.
When we change "dram_base + SZ_512M" to "~0", everything works.
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-02-08 16:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 18:45 [PATCH v3 00/10] arm64: UEFI support Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 01/10] lib: add fdt_empty_tree.c Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 02/10] doc: efi-stub.txt updates for ARM Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 03/10] efi: add helper function to get UEFI params from FDT Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 04/10] arm64: Add function to create identity mappings Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 05/10] efi: Add shared FDT related functions for ARM/ARM64 Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 06/10] arm64: efi: add EFI stub Leif Lindholm
2014-04-09 14:20 ` Mark Rutland
2014-04-10 12:54 ` Mark Salter
2017-02-08 16:28 ` Timur Tabi
2017-02-08 16:29 ` Ard Biesheuvel
2017-02-08 16:35 ` Timur Tabi [this message]
2017-02-08 17:03 ` Mark Rutland
2017-02-08 17:22 ` Jeffrey Hugo
2017-02-08 17:30 ` Jeffrey Hugo
2017-02-08 17:34 ` Mark Rutland
2017-02-08 17:40 ` Ard Biesheuvel
2014-04-04 18:45 ` [PATCH v3 07/10] doc: arm64: add description of EFI stub support Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 08/10] arm64: add EFI runtime services Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 09/10] doc: arm: add UEFI support documentation Leif Lindholm
2014-04-04 18:45 ` [PATCH v3 10/10] efi/arm64: ignore dtb= when UEFI SecureBoot is enabled Leif Lindholm
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=73a460e5-98f5-86c2-142f-a9a084ee0203@codeaurora.org \
--to=timur@codeaurora.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).