Bug 110423

Summary: Forced EDID is ignored
Product: DRI Reporter: Heiko Lechner <Heiko.Lechner>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: harry.wentland, nicholas.kazlauskas
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
output from edid-decode from hacked EDID file none

Description Heiko Lechner 2019-04-14 20:15:55 UTC
Created attachment 143968 [details]
output from edid-decode from hacked EDID file

I have a tv that does not handle YCbCr properly but advertises it in his EDID. So I have to force Full RGB over HDMI because it seems that my RX 570 uses YCbCr by default (maybe because of the HDMI connection?).
There is no switch to force Full RGB so I downloaded the EDID with get-edid using i2c and hacked it to disable the advertisement of YcbCr. I copied it to the initrd and force loaded it via drm.edid_firmware=edid/PhilipsFTV.bin.
It works:
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-trunk-amd64 root=UUID=1c91ef55-0cf6-4694-bd2a-29aeb6492b3b ro drm.edid_firmware=edid/PhilipsFTV.bin
[    0.849967] platform HDMI-A-1: firmware: direct-loading firmware edid/PhilipsFTV.bin
[    0.850055] [drm] Got external EDID base block and 1 extension from "edid/PhilipsFTV.bin" for connector "HDMI-A-1"

But the problems with my tv persist. So I think that the forced EDID is ignored by AMDGPU.

uname -a:
Linux Heimkino-PC 5.0.0-trunk-amd64 #1 SMP Debian 5.0.7-1~exp1 (2019-03-22) x86_64 GNU/Linux
Comment 1 Heiko Lechner 2019-04-14 20:25:04 UTC
I forgot: using amdgpu.dc=0 seems to respect the forced edid, the tv works fine but then I have no sound, so this is not really a workaround.
Comment 2 Martin Peres 2019-11-19 09:19:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/751.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.