On 5/19/22 02:35, AKASHI Takahiro wrote:
I thought I had sent out my comment when this patch was submitted first time,
but it seems that it has never reached out to ML.
On Sun, Apr 10, 2022 at 04:05:55PM -0500, kev...@freebsd.org wrote:
From: Kyle Evans
Up until commit 5f59518a7b1ae
I thought I had sent out my comment when this patch was submitted first time,
but it seems that it has never reached out to ML.
On Sun, Apr 10, 2022 at 04:05:55PM -0500, kev...@freebsd.org wrote:
> From: Kyle Evans
>
> Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we
>
On Mon, Apr 11, 2022 at 1:14 PM Heinrich Schuchardt wrote:
>
> On 4/10/22 23:05, 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
On 4/10/22 23:05, 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
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
5 matches
Mail list logo
