From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Arnd Bergmann" <arnd@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Helge Deller" <deller@gmx.de>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dummycon: only build module if there are users
Date: Wed, 26 Feb 2025 12:46:56 +0100 [thread overview]
Message-ID: <79d35e3b-9a0d-41a5-ab07-797bfa1e19cb@app.fastmail.com> (raw)
In-Reply-To: <29ecc7c4-2887-4989-a1d3-aa76b44c0387@suse.de>
On Wed, Feb 26, 2025, at 09:16, Thomas Zimmermann wrote:
> Am 26.02.25 um 08:55 schrieb Arnd Bergmann:
> Here's another general question. vgacon and fbcon only seem usable with
> CONFIG_VT=y. Wouldn't it make sense to have them depend on CONFIG_VT=y?
> dummycon could then be implemented as part of the vt code, maybe even
> become a vt-internal thing. The console code is complex, so I'm probably
> missing something here?
I think in theory one may have a system use fbcon purely to get the
boot logo, but not actually support VT. I had also assumed there might
be a way to use fbcon as the console (i.e. printk) but not register
the tty, but it looks like the console code still requires vt.
After I looked at the vt and conswitchp code some more, I wonder
if we could go the other way and instead of integrating it more
make the conswitchp logic optional: most of the complexity here
deals with switching between text console and fbcon dynamically,
but having any text console support is getting very rare (vga
on alpha/mips/x86-32, newport on mips-ip22, sti on parisc).
If we do this, the conswitchp code could be merged with dummycon
in drivers/video/console, with the simpler alternative just
calling into fbcon functions. I'm not sure if we can already drop
vgacon from normal x86-64 distro configs, i.e. if there are cases
that are not already covered by any of efi-earlycon, efifb,
vga16fb, vesafb/uvesafb or a PCI DRM driver.
Arnd
next prev parent reply other threads:[~2025-02-26 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 16:44 [PATCH 1/3] dummycon: only build module if there are users Arnd Bergmann
2025-02-25 16:44 ` [PATCH 2/3] dummycon: fix default rows/cols Arnd Bergmann
2025-02-26 7:54 ` Thomas Zimmermann
2025-02-25 16:44 ` [PATCH 3/3] mdacon: rework dependency list Arnd Bergmann
2025-02-26 8:08 ` Thomas Zimmermann
2025-02-26 7:48 ` [PATCH 1/3] dummycon: only build module if there are users Thomas Zimmermann
2025-02-26 7:53 ` Thomas Zimmermann
2025-02-26 7:55 ` Arnd Bergmann
2025-02-26 8:16 ` Thomas Zimmermann
2025-02-26 11:46 ` Arnd Bergmann [this message]
2025-02-26 12:05 ` Javier Martinez Canillas
2025-02-26 13:18 ` Arnd Bergmann
2025-02-26 16:35 ` Helge Deller
2025-02-27 9:25 ` Thomas Zimmermann
2025-03-09 1:46 ` Helge Deller
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=79d35e3b-9a0d-41a5-ab07-797bfa1e19cb@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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