From: Alan Mackenzie <acm@muc.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Simona Vetter <simona@ffwll.ch>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: More than 256/512 glyphs on the Liinux console
Date: Thu, 27 Aug 2026 19:23:29 +0000 [thread overview]
Message-ID: <apCOsfuSYkaI8A1r@MAC.fritz.box> (raw)
In-Reply-To: <2025022243-street-joylessly-6dfa@gregkh>
[ Following a break of ~18 months ]
On Sat, Feb 22, 2025 at 09:48:32 +0100, Greg Kroah-Hartman wrote:
> On Fri, Feb 21, 2025 at 03:35:59PM +0000, Alan Mackenzie wrote:
> >
> > Dear Linux Maintainers,
> >
> > The Linux console is currently restricted to 256/512 glyphs, the VGA
> > standard from the 1980s. I would like that restriction to be lifted, and
> > believe that many other console users would agree.
> First off, why? What about the move to get rid of the vt code entirely,
> if you do that, can't you get proper glyphs with the drm subsystem?
We talked back then about kmscon. It doesn't look to me to be a
suitable replacement for the Linux console yet, at least for me anyway,
for quite a few reasons.
> Doing huge changes for a subsystem that almost everyone agrees should
> only be kept around for legacy reasons is a rough undertaking.
> <snip>
> > I would very much like further to develop and to refine this code to the
> > point where it is suitable for inclusion in the mainline kernel. What do
> > you say?
> Only you can decide what you want to work on. If you have working
> patches, and submit them so that they can be reviewed, we'll be glad to
> do so.
I've just submitted a series of patches to a few mailing lists and
several people, including yourself.
> But again, you are going to have to answer the reason "why" first.
The main reason I don't like kmscon (yet) is that it has no key bindings
<Alt>-<Fn> to switch to a specific VT (or something analogous). This
would make it unusable for my current work flow, where I have 20 tty's
running, and switch between them frequently using <Alt>-<Fn> or
<Shift>-<Alt>-<Fn>.
Even though kmscon has been included in some distributions (including
Fedora), I have failed to find any user reviews of it in a web search.
In particular, I'm looking for somebody writing something like "I've
been using kmscon for <n> weeks, and I find it delightful.".
> thanks,
> greg k-h
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2026-08-27 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:35 Alan Mackenzie
2025-02-22 8:48 ` Greg Kroah-Hartman
2025-02-22 15:36 ` Alan Mackenzie
2025-02-23 7:47 ` Greg Kroah-Hartman
2025-02-24 18:22 ` Alan Mackenzie
2025-02-24 20:08 ` Jiri Slaby
2025-02-25 4:32 ` Greg Kroah-Hartman
2025-02-25 16:15 ` Alan Mackenzie
2025-02-26 10:09 ` Greg Kroah-Hartman
2025-02-26 11:14 ` Jiri Slaby
2025-02-27 13:05 ` Alan Mackenzie
2025-03-01 4:24 ` Greg Kroah-Hartman
2025-03-04 20:30 ` Alan Mackenzie
2025-03-01 7:49 ` Jiri Slaby
2026-08-27 19:23 ` Alan Mackenzie [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-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=apCOsfuSYkaI8A1r@MAC.fritz.box \
--to=acm@muc.de \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®