From: "Pete Batard" <pete@akeo.ie>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>, devel@edk2.groups.io
Cc: leif@nuviainc.com
Subject: Re: [edk2-platforms][PATCH 1/1] Platform/RaspberryPi: Revert don't connect all devices on an ordinary boot
Date: Mon, 8 Jun 2020 18:24:01 +0100 [thread overview]
Message-ID: <6fa3746e-2951-31c0-ab1b-5f175b3d4d5b@akeo.ie> (raw)
In-Reply-To: <0c1125b9-146a-2b1c-e8b2-bade49ff7620@arm.com>
On 2020.06.08 18:10, Ard Biesheuvel wrote:
> On 6/8/20 7:01 PM, Pete Batard wrote:
>> On 2020.06.08 17:43, Ard Biesheuvel wrote:
>>> On 6/8/20 5:51 PM, Pete Batard wrote:
>>>> This reverts commit c8000ecccc83b728baf04ced2fedb870bc3bc1b3 on account
>>>> of USB keyboard devices not being detected until after the timeout to
>>>> enter the Setup menu or run the UEFI Shell has expired.
>>>>
>>>> The core of the issue is that, when EfiBootManagerConnectAll() is not
>>>> invoked, PCI bus scanning only starts after the BDS wait period has
>>>> elapsed, which effectively takes away the ability to use an USB device
>>>> to enact Boot Device Selection or interact with the Setup menu.
>>>>
>>>> Signed-off-by: Pete Batard <pete@akeo.ie>
>>>
>>> Could we move the call to
>>>
>>> EfiEventGroupSignal (&gEfiEndOfDxeEventGroupGuid);
>>>
>>> to the start of PlatformBootManagerBeforeConsole() instead?
>>
>> Moving EfiEventGroupSignal(&gEfiEndOfDxeEventGroupGuid) early into
>> PlatformBootManagerBeforeConsole() doesn't seem to have any effect, as
>> far as I could test.
>>
>> We can however move the EfiBootManagerConnectAll() there if that's
>> what you are asking.
>>
>
> No, the whole idea was to get rid of EfiBootManagerConnectAll().
>
> You are saying the PCI bus scanning starts after the BDS wait period,
> right? This is strange, I wouldn't expect that. That is why I suggested
> moving the EfiEventGroupSignal() call earlier.
>
> Looking at the ArmPkg version, it appears we need a sequence like
>
> EfiEventGroupSignal (&gEfiEndOfDxeEventGroupGuid);
>
> EfiBootManagerDispatchDeferredImages ();
>
> FilterAndProcess (&gEfiPciRootBridgeIoProtocolGuid, NULL, Connect);
>
> and that last call is missing from the RPi4 implementation.
>
> After those calls, all the PCI I/O handles should be enumerated.
Yup, that seems to work.
I need to test a bit more and clean up, then I'll send a patch to
supersede this one.
Regards,
/Pete
>
>
>>
>>>
>>>
>>>
>>>
>>>> ---
>>>> Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c |
>>>> 5 +++++
>>>> 1 file changed, 5 insertions(+)
>>>>
>>>> diff --git
>>>> a/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
>>>> b/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
>>>> index 253614a646c1..2bd625ad7e7c 100644
>>>> --- a/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
>>>> +++ b/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
>>>> @@ -655,6 +655,11 @@ PlatformBootManagerAfterConsole (
>>>> Print (BOOT_PROMPT);
>>>> }
>>>> + //
>>>> + // Connect the rest of the devices.
>>>> + //
>>>> + EfiBootManagerConnectAll ();
>>>> +
>>>> Status = gBS->LocateProtocol (&gEsrtManagementProtocolGuid,
>>>> NULL, (VOID**)&EsrtManagement);
>>>> if (!EFI_ERROR (Status)) {
>>>> EsrtManagement->SyncEsrtFmp ();
>>>>
>>>
>>
>
next prev parent reply other threads:[~2020-06-08 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 15:51 [edk2-platforms][PATCH 1/1] Platform/RaspberryPi: Revert don't connect all devices on an ordinary boot Pete Batard
2020-06-08 16:43 ` Ard Biesheuvel
2020-06-08 17:01 ` Pete Batard
2020-06-08 17:10 ` Ard Biesheuvel
2020-06-08 17:24 ` Pete Batard [this message]
[not found] ` <1616A175B5F96459.24909@groups.io>
2020-06-09 10:01 ` [edk2-devel] " Pete Batard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fa3746e-2951-31c0-ab1b-5f175b3d4d5b@akeo.ie \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox