[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f847ef3-9fb9-46a1-b5bd-38d8498b7772@0la.ch>
Date: Wed, 26 Nov 2025 15:41:08 +0100
From: Yaroslav <iam@....ch>
To: Jani Nikula <jani.nikula@...ux.intel.com>, Yaroslav Bolyukin
<iam@...h.pw>, Ville Syrjälä
<ville.syrjala@...ux.intel.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>
Cc: Harry Wentland <harry.wentland@....com>, Leo Li <sunpeng.li@....com>,
Rodrigo Siqueira <siqueira@...lia.com>,
Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
Wayne Lin <Wayne.Lin@....com>, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v6 2/7] drm/edid: prepare for VESA vendor-specific data
block extension
On 2025-11-26 15:29, Jani Nikula wrote:
> On Wed, 26 Nov 2025, Yaroslav <iam@....ch> wrote:
> The failure mode is: Someone buys a new shiny laptop with eDP MSO, with
> bigger vendor block, and won't get a picture on screen.
I understand that, I'm only confused because this does seem to be as
suitable for backport as this fixed DSC bpp thing is:
Someone buys a VR headset with fixed DSC bpp (Bigscreen Beyond/Bigscreen
Beyond 2/Vive Pro 2), and the system is unable to detect them.
Unless eDP MSO with vendor specific data block extended with unset fixed
DSC bpp value is much more popular in the wild, that is. I have however
failed to discover any devices which have this value present other than
the three mentioned VR headsets.
> BR,
> Jani.
>
>
Powered by blists - more mailing lists