From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215001] Regression in 5.15, Firmware-initialized graphics console selects FB_VGA16, screen corruption
Date: Wed, 12 Jan 2022 02:14:47 +0000 [thread overview]
Message-ID: <bug-215001-2300-7ACdI2r5DU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215001-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215001
--- Comment #13 from Kris Karas (bugs-a21@moonlit-rail.com) ---
Hi Javier, et al,
I have just tested version two of the patch (from email, I don't see it listed
in the attachments), on the original two BIOS/VGAC servers, one new UEFI
server, and my original UEFI desktop. Once again, I'm happy to report flawless
operation on all four.
Tested-By: Kris Karas <bugs-a21@moonlit-rail.com>
Thanks again, Javier! I hope this one also makes Geert happy, too.
(I'd still be happier if non-X86 would be patched to use orig_video_isVGA as an
integer; but for expediency, this seems fine.)
Kris
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-01-12 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215001-2300@https.bugzilla.kernel.org/>
2021-11-16 9:56 ` [Bug 215001] Regression in 5.15, Firmware-initialized graphics console selects FB_VGA16, screen corruption bugzilla-daemon
2021-11-16 9:57 ` bugzilla-daemon
2022-01-06 2:39 ` bugzilla-daemon
2022-01-06 15:16 ` bugzilla-daemon
2022-01-07 2:16 ` bugzilla-daemon
2022-01-07 2:24 ` bugzilla-daemon
2022-01-07 7:52 ` bugzilla-daemon
2022-01-07 11:13 ` bugzilla-daemon
2022-01-07 11:31 ` bugzilla-daemon
2022-01-07 23:12 ` bugzilla-daemon
2022-01-08 11:16 ` bugzilla-daemon
2022-01-11 9:50 ` bugzilla-daemon
2022-01-12 2:14 ` bugzilla-daemon [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=bug-215001-2300-7ACdI2r5DU@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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