From: Laszlo Ersek <lersek@redhat.com>
To: "Дмитрий Степанов" <stepanov.dmit@gmail.com>, edk2-devel@lists.01.org
Subject: Re: OVMF Logo
Date: Tue, 8 May 2018 12:35:39 +0200 [thread overview]
Message-ID: <e8881e38-4307-f7a2-e60a-cf0f56bad179@redhat.com> (raw)
In-Reply-To: <CA+-SuJ0DZ6omrVQo43SE7+fkvaEV7TRAu7avZpnwbxFDRrGMBA@mail.gmail.com>
Hi Dmitry,
On 05/05/18 12:36, \x14<8B@89 !B5?0=>2 wrote:
> Hello!
> Is it possible to tune Logo's behavior in OVMF? Now it overlaps
> Windows Logo during system boot
Hmmm, generally that shouldn't happen; the logo's location is made
available to windows via the BGRT (boot graphics resource table) ACPI
table. When we added BGRT support to OVMF [*], the location / appearance
of the Windows boot animation did change (because it started considering
the TianoCore logo displayed by OVMF), but I don't recall any actual
*conflict* between the logo & the boot animation.
[*] 6e5e544f227f ("OvmfPkg: Install BGRT ACPI table", 2017-01-06):
> Note from Laszlo Ersek <lersek@redhat.com>: without the BGRT ACPI
> table, Windows 8 and Windows 10 first clear the screen, then display a
> blue, slanted Windows picture above the rotating white boot animation.
> With the BGRT ACPI table, Windows 8 and Windows 10 don't clear the
> screen, the blue Windows image is not displayed, and the rotating
> white boot animation is shown between the firmware's original
> TianoCore boot splash and (optional) "Start boot option" progress bar.
In brief, this shouldn't happen, and if it does, it's not specific to
OVMF -- can you perhaps provide more information so that the
MdeModulePkg maintainers might help with the investigation? What Windows
release? What boot animation exactly? What screen resolution?
Thanks!
Laszlo
next prev parent reply other threads:[~2018-05-08 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 10:36 OVMF Logo Дмитрий Степанов
2018-05-08 10:35 ` Laszlo Ersek [this message]
2018-05-08 13:31 ` Richardson, Brian
2018-05-10 0:20 ` Blibbet
2018-05-10 21:54 ` Richardson, Brian
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=e8881e38-4307-f7a2-e60a-cf0f56bad179@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