From: "Laszlo Ersek" <lersek@redhat.com>
To: Zhichao Gao <zhichao.gao@intel.com>, devel@edk2.groups.io
Cc: Aaron Antone <aanton@microsoft.com>,
Jian J Wang <jian.j.wang@intel.com>, Hao Wu <hao.a.wu@intel.com>,
Ray Ni <ray.ni@intel.com>, Star Zeng <star.zeng@intel.com>,
Liming Gao <liming.gao@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Michael Turner <Michael.Turner@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [PATCH V2 2/2] MdeModulePkg/GraphicsConsoleDxe: Do not clean the screen
Date: Tue, 23 Apr 2019 15:50:36 +0200 [thread overview]
Message-ID: <1e606f64-af5b-494b-e497-eef0b2f0fe7a@redhat.com> (raw)
In-Reply-To: <20190423070450.1892-3-zhichao.gao@intel.com>
On 04/23/19 09:04, Zhichao Gao wrote:
> From: Aaron Antone <aanton@microsoft.com>
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1412
>
> For now, most platform support to display during PEIM. It means the logo
> can show at PEI phase. But the screen would be cleared at BDS connect
> console phase. That may make the screen flush and turn into black screen.
> So do not clear the screen while set the text mode for graphics console
> device for the first time boot.
> As the shell reconnect command would make the same reslut with the first
> boot, use the gEfiEventReadyToBootGuid to distinguish them.
>
> Also replace the debug code in GraphicsConsoleControllerDriverStart. The
> origin one would set a basic mode and then print the text info to graphic
> console device. Then the conspliter would set a best mode for graphics
> console device. If the best mode is different with the basic one, the
> screen would be cleared. So use the debug output instead.
>
> This patch only affect the behavior of SetMode at the first boot during
> the graphics console devices first connect operations. That means at
> DXE phase before ReadyToBoot, the Graphics Simple Text Out SetMode would not
> clear the screen during the first connecttion of the graphics devices.
The UEFI spec requirement doesn't apply after ReadyToBoot only. What
about SysPrep applications, for example:
"""
When launched, the platform is required to provide the application
loaded by SysPrep####, with the same services such as console and
network as are normally provided at launch to applications referenced by
a Boot#### variable. [...] After all SysPrep#### variables have been
launched and exited, the platform shall notify
EFI_EVENT_GROUP_READY_TO_BOOT event group and begin to evaluate Boot####
variables [...]
"""
Thus a SysPrep application is permitted to expect, and to use, the
console, but it is launched before ReadyToBoot; and so this patch could
break the console's std conformance for SysPrep apps.
I guess you have already investigated adding a boolean field to
GRAPHICS_CONSOLE_DEV, and found it unsuitable for those platforms that
need this anti-flicker tweak. So I'm not going to suggest such a boolean
field now.
Instead, I propose a PCD (feature PCD or dynamic boolean PCD). If you
add a PCD, I won't care about the particulars of this patch, as long as
platforms continue observing the std conformant behavior, under the
default value of the PCD (i.e., from "MdeModulePkg.dec").
Thanks,
Laszlo
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao Wu <hao.a.wu@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Michael Turner <Michael.Turner@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Zhichao Gao <zhichao.gao@intel.com>
> ---
> .../GraphicsConsoleDxe/GraphicsConsole.c | 82 +++++++++++++------
> .../GraphicsConsoleDxe/GraphicsConsoleDxe.inf | 3 +
> 2 files changed, 62 insertions(+), 23 deletions(-)
>
> diff --git a/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsole.c b/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsole.c
> index 26ea19f300..39a999838c 100644
> --- a/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsole.c
> +++ b/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsole.c
> @@ -1,7 +1,7 @@
> /** @file
> This is the main routine for initializing the Graphics Console support routines.
>
> -Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
> +Copyright (c) 2006 - 2019, Intel Corporation. All rights reserved.<BR>
> SPDX-License-Identifier: BSD-2-Clause-Patent
>
> **/
> @@ -96,6 +96,12 @@ EFI_DRIVER_BINDING_PROTOCOL gGraphicsConsoleDriverBinding = {
> NULL
> };
>
> +//
> +// Event and variable to indicate the boot phase.
> +//
> +EFI_EVENT mGraphicsConsoleReadyToBootEvent;
> +BOOLEAN mGraphicsConsoleReadyToBoot = FALSE;
> +
> /**
> Test to see if Graphics Console could be supported on the Controller.
>
> @@ -567,16 +573,7 @@ GraphicsConsoleControllerDriverStart (
> //
> Private->SimpleTextOutputMode.MaxMode = (INT32) MaxMode;
>
> - DEBUG_CODE_BEGIN ();
> - Status = GraphicsConsoleConOutSetMode (&Private->SimpleTextOutput, 0);
> - if (EFI_ERROR (Status)) {
> - goto Error;
> - }
> - Status = GraphicsConsoleConOutOutputString (&Private->SimpleTextOutput, (CHAR16 *)L"Graphics Console Started\n\r");
> - if (EFI_ERROR (Status)) {
> - goto Error;
> - }
> - DEBUG_CODE_END ();
> + DEBUG ((DEBUG_INFO, "Graphics Console Started!\n\r"));
>
> //
> // Install protocol interfaces for the Graphics Console device.
> @@ -1366,18 +1363,26 @@ GraphicsConsoleConOutSetMode (
> //
> // The current graphics mode is correct, so simply clear the entire display
> //
> - Status = GraphicsOutput->Blt (
> - GraphicsOutput,
> - &mGraphicsEfiColors[0],
> - EfiBltVideoFill,
> - 0,
> - 0,
> - 0,
> - 0,
> - ModeData->GopWidth,
> - ModeData->GopHeight,
> - 0
> - );
> + //
> + // For the first time boot system, do not clear the display.
> + // Some platforms would show logo at PEIM and this would clear
> + // the whole screen. So for first boot set mode, do not clear
> + // the screen.
> + //
> + if (This->Mode->Mode != -1 || mGraphicsConsoleReadyToBoot) {
> + Status = GraphicsOutput->Blt (
> + GraphicsOutput,
> + &mGraphicsEfiColors[0],
> + EfiBltVideoFill,
> + 0,
> + 0,
> + 0,
> + 0,
> + ModeData->GopWidth,
> + ModeData->GopHeight,
> + 0
> + );
> + }
> }
> } else if (FeaturePcdGet (PcdUgaConsumeSupport)) {
> //
> @@ -2065,6 +2070,24 @@ RegisterFontPackage (
> FreePool (Package);
> }
>
> +/**
> + Indicate the Boot phase is at ReadyToBoot.
> +
> + @param[in] Event The Event that is being processed.
> + @param[in] Context The Event Context.
> +
> +**/
> +VOID
> +GraphicsConsoleReadyToBootEvent (
> + IN EFI_EVENT Event,
> + IN VOID *Context
> + )
> +{
> + mGraphicsConsoleReadyToBoot = TRUE;
> +
> + gBS->CloseEvent (mGraphicsConsoleReadyToBootEvent);
> +}
> +
> /**
> The user Entry Point for module GraphicsConsole. The user code starts with this function.
>
> @@ -2095,6 +2118,19 @@ InitializeGraphicsConsole (
> &mHiiRegistration
> );
>
> + //
> + // Create a event function of ReadyToBoot to avoid clearing screen before boot
> + //
> + Status = gBS->CreateEventEx (
> + EVT_NOTIFY_SIGNAL,
> + TPL_NOTIFY,
> + GraphicsConsoleReadyToBootEvent,
> + NULL,
> + &gEfiEventReadyToBootGuid,
> + &mGraphicsConsoleReadyToBootEvent
> + );
> + ASSERT_EFI_ERROR (Status);
> +
> //
> // Install driver model protocol(s).
> //
> diff --git a/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsoleDxe.inf b/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsoleDxe.inf
> index f7caa65aa9..59751893f6 100644
> --- a/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsoleDxe.inf
> +++ b/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsoleDxe.inf
> @@ -49,6 +49,9 @@
> HiiLib
> PcdLib
>
> +[Guids]
> + gEfiEventReadyToBootGuid ## CONSUMES
> +
> [Protocols]
> gEfiDevicePathProtocolGuid ## TO_START
> gEfiSimpleTextOutProtocolGuid ## BY_START
>
next prev parent reply other threads:[~2019-04-23 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 7:04 [PATCH V2 0/2] MdeModulePkg: Make the screen seamless Gao, Zhichao
2019-04-23 7:04 ` [PATCH V2 1/2] MdeModulePkg/ConSplitterDxe: Optimize the ConSplitterTextOutSetMode Gao, Zhichao
2019-04-23 7:04 ` [PATCH V2 2/2] MdeModulePkg/GraphicsConsoleDxe: Do not clean the screen Gao, Zhichao
2019-04-23 13:50 ` Laszlo Ersek [this message]
2019-04-24 2:37 ` [edk2-devel] " Gao, Zhichao
2019-04-24 10:24 ` Laszlo Ersek
2019-04-24 10:48 ` Laszlo Ersek
2019-04-25 15:21 ` Gao, Zhichao
2019-04-26 1:12 ` Sean
2019-04-26 2:38 ` Gao, Zhichao
2019-04-26 19:25 ` Sean
2019-04-28 0:27 ` Gao, Zhichao
2019-04-30 1:07 ` Sean
2019-04-30 8:58 ` Gao, Zhichao
2019-04-26 18:07 ` Laszlo Ersek
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=1e606f64-af5b-494b-e497-eef0b2f0fe7a@redhat.com \
--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