From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Subject: [PATCH 0/5] console: escape sequence handling improvement
Date: Sun, 8 Nov 2026 10:32:02 +0100 [thread overview]
Message-ID: <20261108093354.1247607-1-a.fatoum@barebox.org> (raw)
The v2026.07.0 update broke arrow key usage in the web demo for some
users. Proper fix is on the riscvemu side, but there's still some things
we can do at the barebox side to make escape sequence handling more
robust.
Ahmad Fatoum (5):
readkey: wait for the rest of an escape sequence
lib: term: ask the terminal when a console can't tell its size
serial: virtio_console: report the console size
console: give each console implementation its own console_ctrlc()
console: keep the keys typed ahead when checking for Ctrl-C
common/console.c | 35 +++++++++++++++++++++++++++++++++
common/console_ctrlc.c | 10 ++++------
common/console_simple.c | 10 ++++++++++
drivers/serial/virtio_console.c | 27 +++++++++++++++++++++++++
include/console.h | 4 ++--
lib/readkey.c | 4 +++-
lib/term.c | 5 +++--
7 files changed, 84 insertions(+), 11 deletions(-)
--
2.47.3
next reply other threads:[~2026-11-08 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 9:32 Ahmad Fatoum [this message]
2026-11-08 9:32 ` [PATCH 1/5] readkey: wait for the rest of an escape sequence Ahmad Fatoum
2026-11-08 9:32 ` [PATCH 2/5] lib: term: ask the terminal when a console can't tell its size Ahmad Fatoum
2026-11-08 9:32 ` [PATCH 3/5] serial: virtio_console: report the console size Ahmad Fatoum
2026-11-08 9:32 ` [PATCH 4/5] console: give each console implementation its own console_ctrlc() Ahmad Fatoum
2026-11-08 9:32 ` [PATCH 5/5] console: keep the keys typed ahead when checking for Ctrl-C Ahmad Fatoum
2026-11-09 9:50 ` [PATCH 0/5] console: escape sequence handling improvement Sascha Hauer
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=20261108093354.1247607-1-a.fatoum@barebox.org \
--to=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox