From: Sean Rhodes <sean@starlabs.systems>
To: grub-devel@gnu.org
Subject: [PATCH 0/2] term: Defer configfile clear on inactive output terminals
Date: Tue, 20 Oct 2026 13:49:04 +0100 [thread overview]
Message-ID: <cover.1792500545.git.sean@starlabs.systems> (raw)
A configfile can run before its target has selected visible output. On EFI,
clearing immediately activates text mode and erases the firmware splash even
when the target proceeds with a hidden-menu autoboot.
Defer the clear on inactive output terminals until they prepare for visible
output. Active terminals retain the existing immediate-clear behaviour. The
second patch adds functional coverage for silent and nested configfiles,
subsequent output, multiple terminals, explicit clears, empty output, and
verbose sleep cursor ordering.
Sean Rhodes (2):
term: Defer configfile clear per output terminal
tests: Exercise deferred configfile clear
Sean Rhodes (2):
term: Defer configfile clear per output terminal
tests: Exercise deferred configfile clear
grub-core/Makefile.core.def | 5 +
grub-core/commands/configfile.c | 3 +-
grub-core/commands/sleep.c | 4 +
grub-core/normal/term.c | 35 +++
grub-core/term/efi/console.c | 19 ++
grub-core/tests/deferred_clear_test.c | 317 ++++++++++++++++++++++++++
grub-core/tests/lib/functional_test.c | 1 +
include/grub/term.h | 11 +
8 files changed, 394 insertions(+), 1 deletion(-)
create mode 100644 grub-core/tests/deferred_clear_test.c
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2026-10-20 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 12:49 Sean Rhodes [this message]
2026-10-20 12:49 ` [PATCH 1/2] term: Defer configfile clear per output terminal Sean Rhodes
2026-10-20 12:49 ` [PATCH 2/2] tests: Exercise deferred configfile clear Sean Rhodes
2026-10-20 18:40 ` [PATCH 0/2] term: Defer configfile clear on inactive output terminals Leo Sandoval via Grub-devel
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-all 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=cover.1792500545.git.sean@starlabs.systems \
--to=sean@starlabs.systems \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.