mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	Jiri Slaby <jirislaby@kernel.org>,
	Simona Vetter <simona@ffwll.ch>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Helge Deller <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: vt: Enlarge the framebuffer glyph size from 16 to 32 bits
Date: Sat, 29 Aug 2026 14:09:52 +0200	[thread overview]
Message-ID: <2026082938-spray-shimmer-9389@gregkh> (raw)
In-Reply-To: <apGc4y8ApYWh4Yr4@MAC.fritz.box>

On Fri, Aug 28, 2026 at 02:36:19PM +0000, Alan Mackenzie wrote:
> On Fri, Aug 28, 2026 at 08:12:16 +0200, Thomas Zimmermann wrote:
> > Hi
> 
> > Am 27.08.26 um 20:38 schrieb Alan Mackenzie:
> > > vt: Enlarge the framebuffer glyph size from 16 to 32 bits.
> 
> > > This allows:
> > >    o - More than 256/512 distinct half-width glyphs (in fact, up to 2^21).
> > >    o - Unicode code points >0xffff (outside the Basic Multilingual Plane).
> > >    o - Coloured glyphs (as before).
> 
> > But what is the use case here? We have excellent support for text and 
> > font rendering in graphical userspace for I18N and L10N.
> 
> GUIs are sub-optimal for pure text work.  A full screen terminal is
> wanted.  The current preeminent user space terminal, kmscon, appears to
> lack the refinements of many decades development of the kernel's
> console.

What is missing from kmscon that the kernel currently supports?  Why not
just make it feature-equal there, and then make these additional changes
there as well?

As others have said, we don't want to add new features to the in-kernel
console mode due to all of the reasons the patch review has shown on
this series already (i.e. complex interactions that end up making the
system broken.)  This is best all done in userspace, where a bug there
will not cause these same problems, right?

> Support for blind users exists in the kernel's console.  I don't know
> how good it is, as I don't (yet) need to use it.

But others use it, so we can't break that, and the fact that you ignored
those codepaths here makes me very worried.

> > In contrast, the kernel's text-mode support is limited and a hotbed for 
> > bugs. IMHO we shouldn't add features, but try to simplify that code base.
> 
> >From a user's point of view, the kernel's console is rock solid and
> dependable; it doesn't crash, and its interfaces don't suddenly change
> with the latest release of KDE or Gnome or whatever.

This has nothing to do with KDE or Gnome, if you have issues with those
projects, please take it up with them and contribute to them to resolve
those issues.  I know they can always use the help.

> As is clear, I think the console's limitations should be eliminated.

And the rest of us feel the kernel console's code should be eliminated
entirely, when ever possible :)

thanks,

greg k-h

  reply	other threads:[~2026-08-29 12:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 18:38 Alan Mackenzie
2026-08-27 18:42 ` [Patch 1/9]: Make consolemap.c handle Unicode planes outside BMP Alan Mackenzie
2026-08-28  4:57   ` Jiri Slaby
2026-08-29 11:51     ` Alan Mackenzie
2026-08-27 18:45 ` [Patch 2/9]: Glyph size: Use GLYPH_SZ/HW rather than hardcoded 2, 1 Alan Mackenzie
2026-08-27 18:47 ` [Patch 3/9]: Replace scr_readw/writew by scr_readg/writeg, etc Alan Mackenzie
2026-08-29 12:11   ` Greg Kroah-Hartman
2026-08-29 13:33     ` Alan Mackenzie
2026-08-27 18:48 ` [Patch 4/9]: Amend internal manipulation of glyph structure Alan Mackenzie
2026-08-27 18:50 ` [Patch 5/9]: vt: Amend three Kconfig files Alan Mackenzie
2026-08-27 18:52 ` [Patch 6/9]: vt: Use u32 and typedef u1632 to handle whole glyphs Alan Mackenzie
2026-08-27 18:54 ` [Patch 7/9]: vt: Handle up to 2^21 glyphs, rather than 256/512 Alan Mackenzie
2026-08-27 18:56 ` [Patch 8/9]: vt: Enhancements to the VT ioctl interface Alan Mackenzie
2026-08-27 18:58 ` [Patch 9/9]: vt: Misc changes, e.g. to #include directives Alan Mackenzie
2026-08-29 12:06   ` Greg Kroah-Hartman
2026-08-28  6:12 ` vt: Enlarge the framebuffer glyph size from 16 to 32 bits Thomas Zimmermann
2026-08-28 14:36   ` Alan Mackenzie
2026-08-29 12:09     ` Greg Kroah-Hartman [this message]
2026-08-29 14:39       ` Alan Mackenzie

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=2026082938-spray-shimmer-9389@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=acm@muc.de \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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®