From: sashiko-bot@kernel.org
To: "Hengyu Liang" <hengyul@cs.unc.edu>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] x86/video: Preserve the default VGA fallback for legacy modes
Date: Tue, 03 Nov 2026 03:20:30 +0000 [thread overview]
Message-ID: <sashiko-outbox-194506@kernel.org> (raw)
In-Reply-To: <20261103031630.2085194-1-hengyul@cs.unc.edu>
> Commit 596b3678326d ("x86/video: Only fall back to vga_default_device()
> without screen info") made video_is_primary_device() rely exclusively
> on screen_info resources whenever any are available.
>
> However, screen_info_resources() also returns legacy I/O and memory
> ranges for VGA text modes. These ranges are not PCI BARs, so
> pci_find_resource() does not find them and the default VGA fallback is
> skipped. As a result, no device is primary in VGA text mode.
>
> On a SeaBIOS QEMU guest with bochs and VKMS, the boot VGA (bochs) loses
> its DRM boot_display attribute. VKMS registers fb0 and bochs registers
> fb1. VKMS is not a PCI device, so it is not primary either. With no
> primary device, fbcon keeps the console on fb0 and never remaps it to
> bochs. This can be checked with:
>
> [ ... ]
> Fixes: 596b3678326d ("x86/video: Only fall back to vga_default_device() without screen info")
> Cc: stable@vger.kernel.org
> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
> Signed-off-by: Hengyu Liang <hengyul@cs.unc.edu>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103031630.2085194-1-hengyul@cs.unc.edu?part=1
prev parent reply other threads:[~2026-11-03 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 3:16 [PATCH v2] x86/video: Preserve the default VGA fallback for legacy modes Hengyu Liang
2026-11-03 3:20 ` sashiko-bot [this message]
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=sashiko-outbox-194506@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=hengyul@cs.unc.edu \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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