On Sat, Apr 9, 2022 at 5:37 AM Heinrich Schuchardt wrote:
>
> On 4/6/22 07:04, kev...@freebsd.org wrote:
> > From: Kyle Evans
> >
> > Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we
> > could boot an arbitrary blob with bootefi. Indeed, efi_run_image() even
> > has a specia
On 4/6/22 07:04, kev...@freebsd.org wrote:
From: Kyle Evans
Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we
could boot an arbitrary blob with bootefi. Indeed, efi_run_image() even
has a special case for missing device paths indicating a payload that
was directly loaded vi
From: Kyle Evans
Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we
could boot an arbitrary blob with bootefi. Indeed, efi_run_image() even
has a special case for missing device paths indicating a payload that
was directly loaded via JTAG, for example.
Restore the ability to
3 matches
Mail list logo