From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Date: Wed, 13 Jan 2021 15:23:18 +0200
Subject: [RFC PATCH 2/3] efi_loader: efi_loader: Replace config option
 for initrd loading
In-Reply-To: <3b33783e-6e99-028e-b23b-52994098b07e@gmx.de>
References: <20210113111149.64567-1-ilias.apalodimas@linaro.org>
 <20210113111149.64567-3-ilias.apalodimas@linaro.org>
 <3b33783e-6e99-028e-b23b-52994098b07e@gmx.de>
Message-ID: <X/70Rizn+VgmleLn@apalos.home>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

> > +	  initrd=<ramdisk> will stop working. The protocol will only be
[...]
> 
> How about
> 
> "Linux v5.7 and later can make use of this option. If the boot option
> selected by the UEFI boot manager specifies an existing file to be used
> as initial RAM disk, a Linux specific Load File2 protocol will be
> installed and Linux 5.7+ will ignore any initrd=<ramdisk> command line
> argument."
> 
> > +	  installed if bootmgr is used and the file is found on the defined
> > +	  path. A boot entry of Boot0001 will try to match Initrd0001 and use
> 
> This does not match the implementation.
> 
> > +	  it. Initrd EFI variable format should be '<dev> <part> <filename>'
> > +	  i.e 'mmc 0:1 boot/initrd'
> 
> "The efidebug command can be used to specify the file with the initial
> RAM disk."

Seems like I missed some text while amending the description. 
Your proposal sounds good I'll update it.

[...]
> 
> In all our other coding this variable is called ret.
> I would prefer to do the same here too.

No problem

Cheers
/Ilias
> 
> Best regards
>