public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
	"cadenkline9@gmail.com" <cadenkline9@gmail.com>
Cc: "discuss@edk2.groups.io" <discuss@edk2.groups.io>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-discuss] Google Summer of Code Interested Student
Date: Fri, 12 Mar 2021 19:51:09 +0100	[thread overview]
Message-ID: <b895053c-98bc-4341-a5f6-16f120718516@redhat.com> (raw)
In-Reply-To: <MWHPR1101MB216035D98D6D9BF0514BAE3ECD6F9@MWHPR1101MB2160.namprd11.prod.outlook.com>

On 03/12/21 06:45, Desimone, Nathaniel L wrote:

> Now, here is the second bug. That BIOS setup menu page that OVMF has
> for configuring the serial port has a field for setting the terminal
> type. But, changing the value in that field doesn't actually change
> the configuration data that is sent to the terminal driver. So the
> terminal driver always ends up using PC_ANSI mode even if the user
> changes that setting. This isn’t a bug in the terminal driver really,
> it’s a bug in OVMF's setup menu implementation. But it does create
> the appearance of a problem in the terminal driver and should be
> fixed as part of this GSoC project. This should be fixed in both he
> OVMF implementation and the MinPlatform implementation.

It's a shortcoming of OVMF's PlatformBootManagerLib.

A solution would be nice where, if a (non-volatile) terminal type
setting existed, that would take effect, but if no such setting existed,
then we'd still automatically add the serial port(s) -- with some
default terminal type -- to the console I/O variables.

ArmVirtQemu's PlatformBootManagerLib works somewhat differently (see the
build-time feature test macro TTY_TERMINAL). I'm not up-to-date on
whether that PlatformBootManagerLib instance handles the Setup TUI-based
terminal type setting correctly.

As far as I can remember, the terminal type has always been hard-coded
in OVMF like this -- I believe it's not a regression (old or recent). I
guess I haven't seen a good PlatformBootManagerLib example on this topic.

Thanks
Laszlo


  reply	other threads:[~2021-03-12 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <P6oo.1615342201438491325.TWFM@groups.io>
     [not found] ` <848a0cdb-accf-5b7c-df59-65a806ea14a7@redhat.com>
2021-03-12  5:45   ` [edk2-discuss] Google Summer of Code Interested Student Nate DeSimone
2021-03-12 18:51     ` Laszlo Ersek [this message]
2021-03-13  2:52       ` Nate DeSimone
     [not found]   ` <166B8219924C8DCE.3757@groups.io>
2021-03-13  2:52     ` Nate DeSimone
2021-03-16 15:23       ` Laszlo Ersek
2021-03-16 23:25         ` Nate DeSimone
2021-03-17 17:14           ` Laszlo Ersek
2021-03-17 12:02         ` Leif Lindholm
2021-03-17 16:00         ` [edk2-devel] " Andrew Fish
2021-03-22 18:31           ` Nate DeSimone
2021-03-22 23:07             ` Andrew Fish

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=b895053c-98bc-4341-a5f6-16f120718516@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