From: "Philip Müller" <philm@manjaro.org>
To: Mario Limonciello <mario.limonciello@amd.com>,
Antheas Kapenekakis <lkml@antheas.dev>,
amd-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Robert Beckett" <bob.beckett@collabora.com>
Subject: Re: [PATCH v2 0/5] drm: panel-backlight-quirks: Do partial refactor and apply OLED fix
Date: Thu, 28 Aug 2025 08:39:16 +0200 [thread overview]
Message-ID: <ac38020d-313e-40cc-be7b-f77c69cb5634@manjaro.org> (raw)
In-Reply-To: <607d5062-1734-46c4-b851-782bd7ad3ec7@amd.com>
On 8/27/25 20:38, Mario Limonciello wrote:
> Can you double check with Phil? I thought there are two affected Zotac
> devices, but I could be wrong. If we can get both in a single go let's
> do it.
Yes, the new model is called G1A1W and has the same panel as G0A1W. We
might still work with the vendor to get a firmware update. However, so
far we can keep the quirk for that model as well. If needed I could send
a patch to remove it.
--
Best, Philip
prev parent reply other threads:[~2025-08-28 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 17:43 Antheas Kapenekakis
2025-08-27 17:43 ` [PATCH v2 1/5] drm: panel-backlight-quirks: Make EDID match optional Antheas Kapenekakis
2025-08-27 17:43 ` [PATCH v2 2/5] drm: panel-backlight-quirks: Convert brightness quirk to generic structure Antheas Kapenekakis
2025-08-27 17:43 ` [PATCH v2 3/5] drm: panel-backlight-quirks: Add secondary DMI match Antheas Kapenekakis
2025-08-27 17:43 ` [PATCH v2 4/5] drm: panel-backlight-quirks: Add brightness mask quirk Antheas Kapenekakis
2025-08-27 17:44 ` [PATCH v2 5/5] drm: panel-backlight-quirks: Add Steam Deck brightness quirk Antheas Kapenekakis
2025-08-27 18:38 ` [PATCH v2 0/5] drm: panel-backlight-quirks: Do partial refactor and apply OLED fix Mario Limonciello
2025-08-27 18:41 ` Antheas Kapenekakis
2025-08-28 6:39 ` Philip Müller [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=ac38020d-313e-40cc-be7b-f77c69cb5634@manjaro.org \
--to=philm@manjaro.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bob.beckett@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=mario.limonciello@amd.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
all inboxes | Powered by JetHome®