> On 8 Feb 2017, at 16:28, Timur Tabi <timur@xxxxxxxxxxxxxx> wrote:
>
>> On Fri, Apr 4, 2014 at 1:45 PM, Leif Lindholm <leif.lindholm@xxxxxxxxxx> 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?
>
How do you reckon this constitutes a limit?
> --
> Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project.
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
