From: "David F." <df7729@gmail.com>
To: devel@edk2.groups.io
Subject: SIMPLE_TEXT_OUTPUT_PROTOCOL and Video Resolution
Date: Tue, 15 Jun 2021 23:32:55 -0700 [thread overview]
Message-ID: <CAGRSmLu-tiPJSfCsGKKt1w6KPtvVr+=-Gry2gVAcqctdVYvuiw@mail.gmail.com> (raw)
In-Reply-To: <CAGRSmLuizR=TQgKQOALmhyZxqTgUxQxP2W7BM5ruG7QjARQPXw@mail.gmail.com>
Hello,
I've found that most implementation of UEFI don't automatically change
the resolution when setting the mode with STOP (Simple Text Output
Protocol) . You can use GOP to change it after the mode but that
causes other problems. For example, using surface pro 7 in this case,
with 4K screen. The default text mode is 342x96 which puts it in
2736x1824 mode which you'd expect and the text is tiny. But now you
set the mode to 0 which is 80x25 and it actually sets the mode to
2736x1824 if not already in that resolution and uses a 80x25 area in
the center of the screen, still tiny text you can hardly read. If you
then say you want GOP in 640x480 mode (which is available as GOP mode
1 on this system, it will make the font larger but you can't see
anything because it's still offset to the middle of the 2736x1824 area
and you're only seeing the 640x480 upper left of that area on the
screen. Likewise if you have it in 342x96 so it's fully in the upper
left corner of the screen and change the mode to say 800x600
(available as GOP mode 2 on this system) it will make the text
readable but the text can go off the screen in both directions because
it's still 342x96 when the 100x31 STOP mode would be the correct one
(which happens to be mode 2 on this system).
Shouldn't setting the STOP mode handle adjusting the resolution since
that's the main reason you want to change the mode so the size shown
on the screen changes to something you can read.
Any tricks? I've tried a bunch of things, resetting the controller,
using the Reset() protocol function, and other things but nothing
works. As soon as you use STOP to set the mode, it is back to high
resolution and using an area centered in the screen and changing the
resolution after that leaves it in the area centered in the high res
screen and not in the upper left area.
Thanks.
next parent reply other threads:[~2021-06-16 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGRSmLuizR=TQgKQOALmhyZxqTgUxQxP2W7BM5ruG7QjARQPXw@mail.gmail.com>
2021-06-16 6:32 ` David F. [this message]
[not found] ` <1688FC67A39CB5DB.19105@groups.io>
2021-06-16 21:45 ` [edk2-devel] SIMPLE_TEXT_OUTPUT_PROTOCOL and Video Resolution David F.
2021-06-16 23:22 ` Andrew Fish
2021-06-23 10:24 ` Laszlo Ersek
2021-06-23 16:57 ` Andrew Fish
2021-06-23 19:23 ` Laszlo Ersek
2021-06-24 0:34 ` David F.
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='CAGRSmLu-tiPJSfCsGKKt1w6KPtvVr+=-Gry2gVAcqctdVYvuiw@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