Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1576693 > unrolled thread

Re: [PATCH v3 06/10] arm64: efi: add EFI stub

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v3 06/10] arm64: efi: add EFI stub Timur Tabi <timur@codeaurora.org> - 2017-02-08 17:40 +0100

#1576693 — Re: [PATCH v3 06/10] arm64: efi: add EFI stub

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.

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web