From: Alan Mackenzie <acm@muc.de>
To: dri-devel@lists.freedesktop.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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: Tue, 4 Mar 2025 20:30:56 +0000 [thread overview]
Message-ID: <Z8djAD5WgpyPTnpa@MAC.fritz.box> (raw)
In-Reply-To: <2025022802-monitor-moneyless-0f84@gregkh>
Hello, dri-devel.
The context of the following post is a thread on Linux kernel lists where
I am proposing to extend the Linux console to handle more than 256/512
distinct glyphs.
On Fri, Feb 28, 2025 at 20:24:33 -0800, Greg Kroah-Hartman wrote:
> On Thu, Feb 27, 2025 at 01:05:15PM +0000, Alan Mackenzie wrote:
> > Hello, Greg.
> > On Wed, Feb 26, 2025 at 11:09:57 +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Feb 25, 2025 at 04:15:38PM +0000, Alan Mackenzie wrote:
> > > > On Mon, Feb 24, 2025 at 21:08:50 +0100, Jiri Slaby wrote:
> > > > > I didn't read the thread, but are you looking e.g. for kmscon?
> > > > No, I wasn't. I was looking for a drm replacement for the
> > > > drivers/tty/vt code inside the kernel. I may have misunderstood
> > > > Greg when he referred to a replacement which uses drm.
> > > No, this is what I was referring to. Also maybe we should be
> > > asking on the drm list? The developers there were working to get
> > > rid of CONFIG_VT so I know they have plans for what they see
> > > replacing it.
Is this (still) the case? Have people on dri-devel developed a Linux
console which supersedes the code in drivers/tty/vt, or are they in the
midst of doing so?
Where can I best inform myself about this, and (possibly) install this
replacement console on my system for my own use?
Thanks for any information!
[ .... ]
> dri-devel@lists.freedesktop.org is the list.
> thanks,
> greg k-h
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2025-03-04 20:31 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
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 [this message]
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=Z8djAD5WgpyPTnpa@MAC.fritz.box \
--to=acm@muc.de \
--cc=dri-devel@lists.freedesktop.org \
--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