Re: Fit images and EFI_LOAD_FILE2_PROTOCOL

2020-10-05 Thread Heinrich Schuchardt
Am 6. Oktober 2020 00:37:58 MESZ schrieb Grant Likely : > > >On 03/10/2020 09:51, Heinrich Schuchardt wrote: >> Hello Ilias, hello Christian, >> >> with commit ec80b4735a59 ("efi_loader: Implement FileLoad2 for >initramfs >> loading") Ilias provided the possibility to specify a device path >> (CON

Re: Fit images and EFI_LOAD_FILE2_PROTOCOL

2020-10-05 Thread Grant Likely
On 03/10/2020 09:51, Heinrich Schuchardt wrote: Hello Ilias, hello Christian, with commit ec80b4735a59 ("efi_loader: Implement FileLoad2 for initramfs loading") Ilias provided the possibility to specify a device path (CONFIG_EFI_INITRD_FILESPEC) from which an initial RAM disk can be served via

Re: Fit images and EFI_LOAD_FILE2_PROTOCOL

2020-10-05 Thread François Ozog
On Mon, 5 Oct 2020 at 17:25, Daniel Thompson wrote: > On Mon, Oct 05, 2020 at 04:12:11PM +0200, François Ozog wrote: > > The driving idea is that there is an existing bootflow, non UEFI that > > allows vmlinuz, initrd and DTB to be protected in a single FIT. The > > trustworthiness of the solutio

Re: Fit images and EFI_LOAD_FILE2_PROTOCOL

2020-10-05 Thread Daniel Thompson
On Mon, Oct 05, 2020 at 04:12:11PM +0200, François Ozog wrote: > The driving idea is that there is an existing bootflow, non UEFI that > allows vmlinuz, initrd and DTB to be protected in a single FIT. The > trustworthiness of the solution is higher that regular distro on pure UEFI > systems but doe

Re: Fit images and EFI_LOAD_FILE2_PROTOCOL

2020-10-05 Thread François Ozog
The driving idea is that there is an existing bootflow, non UEFI that allows vmlinuz, initrd and DTB to be protected in a single FIT. The trustworthiness of the solution is higher that regular distro on pure UEFI systems but does not allow initrd changes as you install stuff. We need to keep in min