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 Feb 2025 13:05:15 +0000 [thread overview]
Message-ID: <Z8BjC_TzuDVaFC_3@MAC.fritz.box> (raw)
In-Reply-To: <2025022652-uptown-cheating-5df8@gregkh>
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.
Which list would that be? There are over 100 occurrences of "DRM" in the
file MAINTAINERS. I am also interested in this. There is a very great
deal of functionality in drivers/tty/vt. It will be quite a task to
replace it.
> > kmscon doesn't seem to be a suitable replacement for the Linux console.
> > According to Wikipedia, it stopped being maintained ~10 years ago. Also,
> > it is a user level program, not a kernel level program, so will only become
> > active later in the boot process than the current console, which is not
> > a good thing. It might well steal key sequences from application
> > programs, the way X and X window managers do, but maybe it doesn't. On
> > Gentoo, kmscon is "masked", i.e. strongly recommended not to be
> > installed, and installable only after taking special measures.
> Yes, it will be "after" the boot console, but that should be it.
What would the boot console be? Some console needs to be in place early
enough to be able to display "Kernel panic - unable to mount the root
partition".
> It shouldn't be stealing any keys away from anything, but rather going
> through the existing apis we have for input devices and the like.
Agreed.
> I don't know why distros seem to not be using it anymore, maybe there's
> something else?
Jiri pointed to some problems yesterday from his point of view as a SuSE
maintainer. Perhaps kmscon just needs bringing back into maintenance. I
haven't actually looked at it yet.
> thanks,
By the way, I'll be away from my email for a few days, so won't be able
to answer any posts in that time.
> greg k-h
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2025-02-27 13:05 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 [this message]
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=Z8BjC_TzuDVaFC_3@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