From: Jani Nikula <jani.nikula@linux.intel.com>
To: Haram Choi <haram@choiharam.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
ville.syrjala@linux.intel.com
Subject: Re: [REGRESSION] 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports
Date: Tue, 04 Aug 2026 16:12:58 +0300 [thread overview]
Message-ID: <4bf694add4bcd5b6361b3f8a827fb8dab9f250eb@intel.com> (raw)
In-Reply-To: <0102019fcb5d411c-e0a555b7-46da-43a1-bd9d-6cb120f58a7f-000000@eu-west-1.amazonses.com>
On Tue, 04 Aug 2026, Haram Choi <haram@choiharam.com> wrote:
> I think I have found the commit. It is not in drivers/pci at all, and
> my previous suspicion of 94555ea9a048 was wrong. Apologies to Simon
> for the noise.
>
> The regression is:
>
> cc6ed470caa2 ("drm/i915/vga: Avoid VGA arbiter during
> intel_vga_disable() for iGPUs")
> Ville Syrjala <ville.syrjala@linux.intel.com>, 2025-12-08
Uh, that's a bit of a bummer. As you can see, I've only acked it,
because quite honestly, I don't fully understand what's going on, but I
fully trust Ville to follow through with any issues it might cause. Like
this one. However, Ville's not available for a few weeks now, and the
commit also does not revert cleanly anymore.
We can either try to hack together some sort of fix/revert, or wait for
Ville's input.
BR,
Jani.
--
Jani Nikula, Intel
next parent reply other threads:[~2026-08-04 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0102019fcb5d411c-e0a555b7-46da-43a1-bd9d-6cb120f58a7f-000000@eu-west-1.amazonses.com>
2026-08-04 13:12 ` Jani Nikula [this message]
[not found] <CAAKWd2_MZSC=A2EHuEw3=eECr1QfaqrhYawW=njt5muk=5sA_A@mail.gmail.com>
2026-08-04 6:01 ` [REGRESSION] 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports Haram Choi
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=4bf694add4bcd5b6361b3f8a827fb8dab9f250eb@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=haram@choiharam.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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