From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by mx.groups.io with SMTP id smtpd.web10.10008.1676277606157028864 for ; Mon, 13 Feb 2023 00:40:06 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: arm.com, ip: 217.140.110.172, mailfrom: pierre.gondois@arm.com) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4945B4B3; Mon, 13 Feb 2023 00:40:48 -0800 (PST) Received: from [10.34.100.128] (pierre123.nice.arm.com [10.34.100.128]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9C2333F881; Mon, 13 Feb 2023 00:40:04 -0800 (PST) Message-ID: <4d1c3209-87d6-546d-e638-b15d0239e8f3@arm.com> Date: Mon, 13 Feb 2023 09:39:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH 1/1] ArmPkg/PlatformBootManagerLib: Add path to boot UEFI Shell over UiApp To: Ard Biesheuvel Cc: devel@edk2.groups.io, ardb+tianocore@kernel.org, leif@nuviainc.com, sami.mujawar@arm.com, patrik.berglund@arm.com, marcin.juszkiewicz@linaro.org References: <20230207090653.395992-1-pierre.gondois@arm.com> From: "PierreGondois" In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello Ard, On 2/9/23 17:57, Ard Biesheuvel wrote: > On Tue, 7 Feb 2023 at 10:07, wrote: >> >> From: Pierre Gondois >> >> The UEFI Shell is a non-active boot option, at the opposite of UiApp. >> If no valid boot option is found, UiApp is selected. UiApp requires a >> human interaction. When installing a new EDKII image in CIs or when >> scripting is required, this is problematic. >> >> If no valid boot option is discovered, add a path to directly go to >> the UEFI Shell where the startup.nsh script is automatically executed. >> The UEFI Shell is launched after connecting possible devices, but >> before the reset that is meant to automatically make them visible. >> >> The new PcdUefiShellDefaultBootEnable must be set to TRUE to enable >> this behaviour. The Pcd is set to false by default. >> > > Is this similar to how we implemented this on RPi4? IIRC, a similar > issue came up there as well. I'm not finding an equivalent for the Rpi4. I see that the BootDiscoveryPolicy was added, but this regards which devices to connect during boot IIUC. The UEFI Shell also seems to have been added to the Boot Manager Menu, but this should not select the UEFI Shell by default. Regards, Pierre