Re: RFC: Boot Discovery Policy
Hi Ard,toggle quoted messageShow quoted text
Thanks for checking this.
Yeah, you're right if the secondary loaders you meant here are OS boot loaders and some applications for system deployment like iPXE.
This change is based on EFI_BOOT_MANAGER_POLICY_PROTOCOL which currently only supports EFI_BOOT_MANAGER_POLICY_NETWORK_GUID and EFI_BOOT_MANAGER_POLICY_CONNECT_ALL_GUID classes, so it only has Minimal, All Network Devices, All Devices options for using the existing classes and code. For block devices, if you see a need, I think you can submit a Code-first Bugzilla ticket and UEFI ECR for the follow-up (adding EFI_BOOT_MANAGER_POLICY_BLOCK_GUID). What do you think?
From: Ard Biesheuvel <email@example.com>
Sent: Saturday, May 8, 2021 1:37 AM
To: Sunny Wang <Sunny.Wang@arm.com>
Cc: Grzegorz Bernacki <firstname.lastname@example.org>; email@example.com; Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>; Marcin Wojtas <firstname.lastname@example.org>; email@example.com; firstname.lastname@example.org; email@example.com; firstname.lastname@example.org; email@example.com
Subject: Re: [edk2-rfc] RFC: Boot Discovery Policy
On Thu, 29 Apr 2021 at 15:54, Sunny Wang <Sunny.Wang@arm.com> wrote:
So the problem is secondary loaders that assume that all peripherals have been connected, right? To me, the options Minimal/All Network Devices/All Devices seems a bit arbitrary - what about block devices?
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.