[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 4/4] linux: ignore FDT unless we need to modify it
From: |
Ard Biesheuvel |
Subject: |
Re: [PATCH 4/4] linux: ignore FDT unless we need to modify it |
Date: |
Fri, 23 Oct 2020 15:12:50 +0200 |
On Fri, 23 Oct 2020 at 14:47, Leif Lindholm <leif@nuviainc.com> wrote:
>
> On Fri, Oct 23, 2020 at 14:08:25 +0200, Ard Biesheuvel wrote:
> > Now that we implemented supported for the LoadFile2 protocol for initrd
> > loading, there is no longer a need to pass the initrd parameters via
> > the device tree. This means there is no longer a reason to update the
> > device tree in the first place, and so we can ignore it entirely.
>
> There is a change in behaviour here which I don't think matters, but
> I'll call it out anyway:
> If there was ever a kernel out there with an EFI stub that depended on
> a chosen node existing in the DT, and the one provide by firmware did
> not contain one, that setup would break from this *if* it didn't use
> an initrd.
>
I checked the Linux source, and the original code contributed by Roy
already contained the logic to create the /chosen node if it wants
there already. So we should be fine here.
- [PATCH 0/4] linux: implement LoadFile2 initrd loading, Ard Biesheuvel, 2020/10/23
- Re: [PATCH 0/4] linux: implement LoadFile2 initrd loading, Leif Lindholm, 2020/10/23
- [PATCH 1/4] loader/linux: permit NULL argument for argv[] in grub_initrd_load(), Ard Biesheuvel, 2020/10/23
- [PATCH 3/4] efi: implemented LoadFile2 initr loading protocol for Linux, Ard Biesheuvel, 2020/10/23
- [PATCH 2/4] efi: add definition of LoadFile2 protocol, Ard Biesheuvel, 2020/10/23
- [PATCH 4/4] linux: ignore FDT unless we need to modify it, Ard Biesheuvel, 2020/10/23