Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1576693
| From | Timur Tabi <timur@codeaurora.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3 06/10] arm64: efi: add EFI stub |
| Date | 2017-02-08 17:40 +0100 |
| Message-ID | <t8DrH-2DS-5@gated-at.bofh.it> (permalink) |
| References | <n3hlD-6qx-3@gated-at.bofh.it> <n3hlD-6qx-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Apr 4, 2014 at 1:45 PM, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> +/*
> + * EFI entry point for the arm/arm64 EFI stubs. This is the entrypoint
> + * that is described in the PE/COFF header. Most of the code is the same
> + * for both archictectures, with the arch-specific code provided in the
> + * handle_kernel_image() function.
> + */
> +unsigned long __init efi_entry(void *handle, efi_system_table_t *sys_table,
> + unsigned long *image_addr)
> +{
...
> +
> + 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?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH v3 06/10] arm64: efi: add EFI stub Timur Tabi <timur@codeaurora.org> - 2017-02-08 17:40 +0100
csiph-web