From: Hou Qiming <hqm03ster@gmail.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Gerd Hoffmann <kraxel@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: Thu, 23 Apr 2020 11:15:50 +0800 [thread overview]
Message-ID: <CABSdmrk5SYLNDBwLsmrOkx+JcyrfCFjWto-ErBvZSGutzLtHYw@mail.gmail.com> (raw)
In-Reply-To: <de03e16a-df14-c18b-31a0-ec025e7b2b65@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
>
>
> > And when the user provides an EDID one should parse it and set the
> default
> > resolution to match it. But that's a less important feature.
>
> It's more complex than you might think, and (to me personally) it seems
> to require more time than its importance justifies.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1749250
>
>
Read the thread. Actually, I wrote some EDID parsing code a while ago, but
that's before QEMU supporting EDID so I had to do it outside QEMU and pass
my parsing result to ramfb as the now-removed starting_width /
starting_height. In the context QEMU, the EDID actually reflects the user
preference since the whole structure is usually made up from the
user-specified resolution. And I think most guest OSes initialize
first-time-seen monitors to their EDID resolution, which should have
motivated QEMU to provide an EDID for a virtual monitor.
But at this point it's kind of awkward to do the EDID / resolution handling
(that I need) in the ramfb driver as the kvmgt EDID has to be read out from
the i915 MMIO just like a physical GPU. Guess now my use case is better
covered with a fully functional i915 framebuffer driver for OVMF. If I had
the time...
[-- Attachment #2: Type: text/html, Size: 1602 bytes --]
prev parent reply other threads:[~2020-04-23 3:16 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
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 [this message]
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=CABSdmrk5SYLNDBwLsmrOkx+JcyrfCFjWto-ErBvZSGutzLtHYw@mail.gmail.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