AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Timo Prömer" <timo.proemer04@gmail.com>
To: <amd-gfx@lists.freedesktop.org>
Subject: Question about HF-EEODB EDID extension override handling
Date: Tue, 07 Jul 2026 12:06:42 +0200	[thread overview]
Message-ID: <DJS97B8F8T0P.3VZ24NB8R2DLY@gmail.com> (raw)

Hi,

I am trying to get my Samsung Odyssey Neo G8 to run on 3840x2160@240Hz
over HDMI 2.1 (Linux 7.2-rc2), but that mode does not show up.

I noticed that the EDID only contains block 0 and 1,
even though the HF-EEODB specifies an extension block count of 3.

From my reading, the EDID parsing code in 'drivers/gpu/drm/drm_edid.c' 
does respect this override as far as i can tell.
However I also found some code that appears to be copying / truncating the 
EDID in 'drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c:1208'
(function: 'dm_helpers_read_local_edid') without accounting for this override.

I am new to kernel-level development, so I apologize in advance if I 
am misunderstanding the intended flow here. Could this be the reason for
my incomplete EDID? The kernel does not log any EDID-related errors or
warnings, so I am not sure whether this is expected behavior or a bug.

Please keep me on Cc; I am not subscribed to the list.

Thanks,
Timo Prömer

                 reply	other threads:[~2026-07-07 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DJS97B8F8T0P.3VZ24NB8R2DLY@gmail.com \
    --to=timo.proemer04@gmail.com \
    --cc=amd-gfx@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