Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Javier Martinez Canillas" <javierm@redhat.com>,
	"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 14:18:46 +0100	[thread overview]
Message-ID: <98ed694b-0f2f-4bfb-9280-729842d9f95c@app.fastmail.com> (raw)
In-Reply-To: <87mse8zzb0.fsf@minerva.mail-host-address-is-not-set>

On Wed, Feb 26, 2025, at 13:05, Javier Martinez Canillas wrote:
> "Arnd Bergmann" <arnd@arndb.de> writes:
>> 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.
>>
>
> I believe vgacon is still useful for x86 with legacy BIOS, because
> vesafb (and simpledrm) only works if the user defines a mode using
> the vga= kernel cmdline parameter.

Right, at the minimum, a configuration without vgacon would
have to pick a graphical mode in arch/x86/boot/video*.c if one
wasn't already set by grub.

Looking through the git history of that code, it seems that there
are lots of corner cases with weird 32-bit hardware.
Anything from the past 20 years is probably reasonably safe,
but there still needs to be a way to configure vgacon back in
to be safe.

    Arnd

  reply	other threads:[~2025-02-26 13:19 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
2025-02-26 12:05         ` Javier Martinez Canillas
2025-02-26 13:18           ` Arnd Bergmann [this message]
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=98ed694b-0f2f-4bfb-9280-729842d9f95c@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=javierm@redhat.com \
    --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