From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: Harry Wentland <harry.wentland@amd.com>,
Alex Deucher <alexdeucher@gmail.com>,
Steven J Abner <pheonix.sja@att.net>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernels >= 6.3 disable video output
Date: Fri, 16 May 2025 17:02:47 +0200 [thread overview]
Message-ID: <ba97cecf-d820-4ae7-98ae-2cf57db228fb@mailbox.org> (raw)
In-Reply-To: <df6872b3-1048-416b-82d7-63f732cb6b4d@amd.com>
On 2025-05-15 19:59, Harry Wentland wrote:
> Hi Steven,
>
> thanks for the bisect.
>
> In order to avoid display artifacts (especially for HDR) we had to
> allow higher bit depth color output on the wire. The driver should
> fallback to a lower resolution as needed but looks like there's a
> bug with this particular TV. Are you able to share the specific
> TV model? We haven't seen this bug in internal testing but if we
> know which device shows the issue we might be able to find one
> for testing.
>
> It would probably be good if we had a module parameter to force
> limit the output bpc in order to unblock users (like you) that see
> issues.
FWIW, with GNOME the "max bpc" property value can be set per monitor in the ~/.config/monitors.xml file. Other DEs might have something similar (with Xorg, it should even be possible to set it with xrandr).
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
next prev parent reply other threads:[~2025-05-16 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6DWYVS.BXJ4YUZ0KN5B3.ref@att.net>
2025-05-09 0:07 ` Kernels >= 6.3 disable video output Steven J Abner
2025-05-09 13:11 ` Alex Deucher
2025-05-09 13:39 ` Steven J Abner
2025-05-09 14:05 ` Alex Deucher
2025-05-09 14:38 ` Steven J Abner
2025-05-09 15:01 ` Steven J Abner
2025-05-12 20:07 ` Steven J Abner
2025-05-12 20:10 ` Alex Deucher
2025-05-15 16:11 ` Steven J Abner
2025-05-15 16:16 ` Alex Deucher
2025-05-15 17:59 ` Harry Wentland
2025-05-15 18:42 ` Steven J Abner
2025-05-16 15:02 ` Michel Dänzer [this message]
2025-05-16 15:38 ` Steven J Abner
2025-05-16 15:56 ` Steven J Abner
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=ba97cecf-d820-4ae7-98ae-2cf57db228fb@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=pheonix.sja@att.net \
/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