Re: [PATCH v6 2/7] drm/edid: prepare for VESA vendor-specific data block extension

[Yaroslav <iam@0la.ch>]

On 2025-11-26 15:47, Jani Nikula wrote:
> On Wed, 26 Nov 2025, Yaroslav <iam@0la.ch> wrote:
>> On 2025-11-26 15:29, Jani Nikula wrote:
>>> On Wed, 26 Nov 2025, Yaroslav <iam@0la.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.
> 
> The difference is between an existing and enabled feature working vs. a
> new feature working. eDP MSO is expected to work. Also, IIUC you can
> still use the VR headsets albeit with a lower resolution. For eDP MSO
> you simply get nothing, and even beginning to debug the issue is
> problematic, since that is quite possibly the only display on the
> device.
> 

You can use Vive Pro 2 with a lower resolution, but there is no lower 
resolution option present for BSB/BSB2, their support is always borked 
without this patch, and they are more popular in the linux community.

> 
> BR,
> Jani.
> 
>