From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: valerij zaporogeci <vlrzprgts@gmail.com>,
Hou Qiming <hqm03ster@gmail.com>,
discuss@edk2.groups.io,
"Marcel Apfelbaum (GMail address)" <marcel.apfelbaum@gmail.com>,
edk2-devel-groups-io <devel@edk2.groups.io>,
qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [edk2-discuss] Load Option passing. Either bugs or my confusion.
Date: Mon, 20 Apr 2020 16:13:03 +0200 [thread overview]
Message-ID: <20200420141303.dxjqgvmzglrjtsly@sirius.home.kraxel.org> (raw)
In-Reply-To: <a972450d-8834-ae87-e4e3-5263a41d1735@redhat.com>
Hi,
> So I would say that the symptom you see is a QEMU v4.1.0 regression. The
> QemuRamfbGraphicsOutputSetMode() function in the OVMF ramfb driver
> certainly needs the QemuFwCfgWriteBytes() call to work, for changing the
> resolution.
Oh? QemuRamfbGraphicsOutputSetMode() can be called multiple times?
How does that happen?
> (1) Registering a device reset handler in QEMU seems sufficient, so that
> QEMU forget about the currently shared RAMFB area at platform reset.
That happens. After system reset you can write configuration again (once).
The guest os should not play with ramfb. It is supposed to be setup by
the firmware (ovmf driver or vgabios rom) as boot display, then never be
re-configured again ...
cheers,
Gerd
next prev parent reply other threads:[~2020-04-20 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18709.1586743215734342129@groups.io>
[not found] ` <11181.1586825080096843656@groups.io>
2020-04-14 14:26 ` [edk2-discuss] Load Option passing. Either bugs or my confusion Laszlo Ersek
[not found] ` <5211.1586899245384995995@groups.io>
2020-04-15 15:05 ` Laszlo Ersek
2020-04-16 4:38 ` Hou Qiming
2020-04-16 14:12 ` Laszlo Ersek
2020-04-17 3:22 ` Hou Qiming
2020-04-20 9:32 ` Laszlo Ersek
2020-04-20 14:19 ` Gerd Hoffmann
2020-04-20 14:13 ` Gerd Hoffmann [this message]
2020-04-21 13:02 ` Laszlo Ersek
2020-04-22 7:42 ` Hou Qiming
2020-04-22 16:05 ` Laszlo Ersek
2020-04-23 3:15 ` Hou Qiming
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=20200420141303.dxjqgvmzglrjtsly@sirius.home.kraxel.org \
--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