linux-kernel - Re: [PATCH 1/3] drm/tests: edid: Fix monitor range limits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ecuofds1.fsf@minerva.mail-host-address-is-not-set>
Date: Thu, 10 Jul 2025 14:09:34 +0200
From: Javier Martinez Canillas <javierm@...hat.com>
To: Maxime Ripard <mripard@...nel.org>, Maarten Lankhorst
 <maarten.lankhorst@...ux.intel.com>, Thomas Zimmermann
 <tzimmermann@...e.de>, David Airlie <airlied@...il.com>, Simona Vetter
 <simona@...ll.ch>
Cc: Dmitry Baryshkov <lumag@...nel.org>, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org, Maxime Ripard <mripard@...nel.org>
Subject: Re: [PATCH 1/3] drm/tests: edid: Fix monitor range limits

Maxime Ripard <mripard@...nel.org> writes:

> For some reason, some EDIDs used by kunit had Monitor Range Limits
> making no sense, and not matching the edid-decode output in the comment.
>
> While they were in the comments as:
>     Display Range Limits:
>       Monitor ranges (GTF): 50-70 Hz V, 30-70 kHz H, max dotclock 150 MHz
>
> They were actually:
>     Display Range Limits:
>       Monitor ranges (GTF): 50-70 Hz V, 0-0 kHz H, max dotclock 1960 MHz
>
> Fix that section of the EDIDs to match the expected edid-decode output.
>
> Signed-off-by: Maxime Ripard <mripard@...nel.org>
> ---

Reviewed-by: Javier Martinez Canillas <javierm@...hat.com>

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat