All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Alan Mackenzie <acm@muc.de>, 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: Tue, 25 Feb 2025 05:32:46 +0100	[thread overview]
Message-ID: <2025022528-humble-chatter-4e7d@gregkh> (raw)
In-Reply-To: <d5e05c61-d796-4e5c-9538-a1e068631bba@kernel.org>

On Mon, Feb 24, 2025 at 09:08:50PM +0100, Jiri Slaby wrote:
> On 24. 02. 25, 19:22, Alan Mackenzie wrote:
> > Hello, Greg.
> > 
> > On Sun, Feb 23, 2025 at 08:47:53 +0100, Greg Kroah-Hartman wrote:
> > > On Sat, Feb 22, 2025 at 03:36:12PM +0000, Alan Mackenzie wrote:
> > > > On Sat, Feb 22, 2025 at 09:48:32 +0100, Greg Kroah-Hartman wrote:
> > 
> > [ .... ]
> > 
> > > > But I think you are also asking why I use the console at all.  That's
> > > > a fair question which I'll try to answer.
> > 
> > > I'm not disputing using the console, it's the vt layer that I'm talking
> > > about.  The DRM developers have the long-term goal of getting rid of
> > > CONFIG_VT which will remove a ton of mess that we have overall.
> > > DRM-based consoles should provide the same functionality that a vt
> > > console does today.  If not, please let them know so that the remaining
> > > corner cases can be resolved.
> > 
> > Does a DRM based console exist at the moment?  I spent quite some time
> > looking for it yesterday, but found nothing.
> 
> I didn't read the thread, but are you looking e.g. for kmscon?

Yes, that is what I was referring to, but couldn't remember the name,
thanks for the pointer.

greg k-h

  reply	other threads:[~2025-02-25  4:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 15:35 More than 256/512 glyphs on the Liinux console 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 [this message]
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

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=2025022528-humble-chatter-4e7d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=acm@muc.de \
    --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 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.