From: "Andrew Fish via groups.io" <afish=apple.com@groups.io>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [edk2-devel] VT100 terminal for UEFI shell
Date: Thu, 07 Sep 2023 13:10:18 -0700 [thread overview]
Message-ID: <59F39103-6442-4D34-9CB0-ECFDDFE31DF3@apple.com> (raw)
In-Reply-To: <a92bca46-c8d5-47b0-8b2d-aefad924d1ac@linaro.org>
> On Sep 7, 2023, at 12:11 PM, Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> wrote:
>
> W dniu 7.09.2023 o 19:40, Andrew (EFI) Fish pisze:
>>> On Sep 7, 2023, at 8:00 AM, Marcin Juszkiewicz wrote:
>>>
>>> Is there a way to have VT100 (or any other black/white, non-ANSI) terminal for UEFI Shell?
>>>
>>> I do many runs of QEMU/sbsa-ref with logging and all those ANSI colour codes only make problems.
>
>
>> Thus we get to the TL;DR part… The console NVRAM variables that point to the UART has a MESSAGING_DEVICE_PATH MSG_VENDOR_DP node after the UART definition that has a UUID (EFI_GUID) that defines the type of terminal emulation to use.
>> The definition of the ConIn and ConOut variables is here [4]
>
> Feels like adding alias into ~/.bashrc is easier solution:
>
> alias strip_ansi=" sed -e 's/\x1b\[[0-9;]*m//g' "
>
Well like everything the terminal default is optimized for the personal preference of who ever did OVMF port.
> EDK2 code feels like ancient Perl to me too often. Someone wrote it, everyone uses it, hard to find someone who know why it is that way.
>
>
Feel free to ask I’ll probably be 24 years into at some point soon or maybe already I kind of forgot when I started. I was around for most of the big picture stuff so that is one of the reasons I answer these general questions on the list.
Thanks,
Andrew Fish
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108416): https://edk2.groups.io/g/devel/message/108416
Mute This Topic: https://groups.io/mt/101216135/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-09-07 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 15:00 [edk2-devel] VT100 terminal for UEFI shell Marcin Juszkiewicz
2023-09-07 17:40 ` Andrew Fish via groups.io
2023-09-07 19:11 ` Marcin Juszkiewicz
2023-09-07 20:10 ` Andrew Fish via groups.io [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=59F39103-6442-4D34-9CB0-ECFDDFE31DF3@apple.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