Re: [v2,0/5] firmware-owned devicetree for EBBR / SystemReady IR
Simon Glass <[email protected]>
| Newsgroups | org.u-boot-project.lists.u-boot |
|---|---|
| Message-ID | <CAFLszTgX08U3GpcvwkvzBinY7X21EC_P2nEZPx3ikVH=vBt_yA@mail.gmail.com> |
Hi Carlo, On 2026-07-28T13:20:42, Carlo Caione <[email protected]> wrote: > Patch 1 makes an FDT passed to efi_bootmgr_run() outrank a Boot#### FDT, > as an independent behaviour fix. Patch 2 adds the loader, binding, > documentation and shared EFI staging policy. Patches 3 and 4 integrate > the EFI bootmeth and boot manager. Patch 5 adds sandbox coverage. [..] > - 'fw_fdt_part' can pin an A/B partition and 'fw_fdt_config' can select > an explicit configuration. Just to check - is exposing these as environment variables really the right long-term interface? U-Boot has been moving configuration into the control devicetree, and both of these look like properties that would sit naturally on the u-boot,firmware-fdt-block node, with the env var overriding for A/B slot selection only. What do you think? Regards, Simon