From mboxrd@z Thu Jan 1 00:00:00 1970 From: AKASHI Takahiro Date: Wed, 9 Dec 2020 10:42:46 +0900 Subject: [RFC] Testing EFI_CAPSULE_ON_DISK In-Reply-To: <29f27773-73a7-14b1-217b-f4964b969a8b@gmx.de> References: <29f27773-73a7-14b1-217b-f4964b969a8b@gmx.de> Message-ID: <20201209014246.GA27590@laputa> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Heinrich, On Tue, Dec 08, 2020 at 10:46:15PM +0100, Heinrich Schuchardt wrote: > Hello Takahiro > > when I select EFI_CAPSULE_ON_DISK_EARLY this implies EFI_SETUP_EARLY. > > With EFI_SETUP_EARLY I cannot use PREBOOT to add a disk via the host > command. So I do not see how the feature could be tested on the sandbox. I have noticed this issue. In sandbox test case, a disk will be attached via "host bind" command, and so EFI_SETUP_EARLY is simply unusable. Instead, the trick is that the current python script performs > if not capsule_early: > # need to run uefi command to initiate capsule handling > output = u_boot_console.run_command( > 'env print -e -all Capsule0000') after rebooting U-Boot. So at least temporarily you have to turn off EFI_CAPSULE_ON_DISK_EARLY, and do the similar thing in PREBOOT. > I think we will have to enable dynamic binding of block devices to > overcome this mutual blocking of features. I'm not sure yet how the scenario looks like here, but as far as "dynamic binding" is concerned, I have submitted the patch of this exact feature to support plug-in/removable devices (like usb stick and cd-rom) more than two years ago. https://lists.denx.de/pipermail/u-boot/2018-November/346740.html > > What are your ideas? Or simply, we'd better move efi_obj_list_init() backward just before efi_launch_capsules() in main_loop() if it is feasible. Thanks, -Takahiro Akashi > Best regards > > Heinrich