public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Hou Qiming <hqm03ster@gmail.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	valerij zaporogeci <vlrzprgts@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:19:40 +0200	[thread overview]
Message-ID: <20200420141940.tpkhv6zqjkv25h5i@sirius.home.kraxel.org> (raw)
In-Reply-To: <CABSdmr=u9QeNA6jy29e2pkiqnGH=xw1n+Hkkrd=AH1RRvj92Ng@mail.gmail.com>

  Hi,

> The proper way to enable ramfb resolution change again is adding sanity
> checks for ramfb resolution / pointer / etc. on the QEMU side.

Pointer *is* checked.  ramfb creates a mapping, and if that fails due to
the pointer not being valid it bails out.

Sanity-checking the resolution is the job of the UI code.

cheers,
  Gerd


  parent reply	other threads:[~2020-04-20 14:19 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 [this message]
2020-04-20 14:13         ` Gerd Hoffmann
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=20200420141940.tpkhv6zqjkv25h5i@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