From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.0la.ch (mail.0la.ch [78.47.82.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BEB60306B12 for ; Wed, 26 Nov 2025 14:54:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=78.47.82.197 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764168866; cv=none; b=fJ/aLej+42TdzL4uyUx2xvl7QTjF3jLYa24g2XkgoLbxmBDO0G6hNxM/7BWzIsQz6gZpdGz59FYNOXnAharyzuPGAX8yCw1uHKkvgvSFeCq2vMhWc7vrVQib/hjdFYfH/yzm7II+4heNEVoGmZ9w5itNpwO+ZEJVkonMlZlLX5E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764168866; c=relaxed/simple; bh=hKLXEC88QuKdW8+L3Lkj+Z5crsWyPnHTKzAuCJSqQwc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=kVgBNirFdDTu2nYfe2h6ypJ+IHt/EU+F2RS0fRsusqpb2ULrI3zQsqlNk7Mp4EcZPitExwzPUD3aFqK3EMraeYI6I0mQUAdYW3RGCrcYcfp/8rqjSzOv5m3X8TlIr97qtANByiQygm9RQ15HtKSnPm5cy2U6JW+VxF2UHrnF1mI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=0la.ch; spf=pass smtp.mailfrom=0la.ch; dkim=pass (2048-bit key) header.d=0la.ch header.i=@0la.ch header.b=Aubtz6lm; dkim=permerror (0-bit key) header.d=0la.ch header.i=@0la.ch header.b=OaYbGVP5; arc=none smtp.client-ip=78.47.82.197 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=0la.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=0la.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=0la.ch header.i=@0la.ch header.b="Aubtz6lm"; dkim=permerror (0-bit key) header.d=0la.ch header.i=@0la.ch header.b="OaYbGVP5" DKIM-Signature: v=1; a=rsa-sha256; s=202502r; d=0la.ch; c=relaxed/relaxed; h=From:To:Subject:Date:Message-ID; t=1764168836; bh=9Pj3qeZuflG024REHkBYQeO dTaplXLFyxwiJ+sTSIGo=; b=Aubtz6lmdq0SyktKIAtbjd4qCJHLfKmfW22RnUN5c5eG1lABEO ozq94uoH90z1dquya7feqW/acl69cJi0Ceo0csV93QuSAxJ8BmqRyXZvDibCp7pQKYpKlUklLkh T0+fnDQASdIqHeZVa+xCS02zOh/vEDNQsXpntCxkiQdEUXrDKzmRptz6hJnYkYY9olFBto8iJsZ SOaMrHa6sZvfWNVx9ggHNLUAM/32crtu5YSeTRVZyTJYQQwL/MTCQrRaWBGaKwfNvcsXb+csaXI CgfA+VD7hhDEvo/kvdjlUiJvA0p6wrkhdWvp12jmHS90Dh7PSYX8blEhYFFpZeaQo2A==; DKIM-Signature: v=1; a=ed25519-sha256; s=202502e; d=0la.ch; c=relaxed/relaxed; h=From:To:Subject:Date:Message-ID; t=1764168836; bh=9Pj3qeZuflG024REHkBYQeO dTaplXLFyxwiJ+sTSIGo=; b=OaYbGVP57fqLhw1a1LYbZP0VvlWdEMJRL7T5K6D+uTrcTDC9G/ 33nJwBwR+QsRBnKpuPFXh9xdUSPTDx/oCMDw==; Message-ID: Date: Wed, 26 Nov 2025 15:53:55 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v6 2/7] drm/edid: prepare for VESA vendor-specific data block extension To: Jani Nikula , Yaroslav Bolyukin , =?UTF-8?B?VmlsbGUgU3lyasOkbMOk?= , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter Cc: Harry Wentland , Leo Li , Rodrigo Siqueira , Alex Deucher , =?UTF-8?Q?Christian_K=C3=B6nig?= , Wayne Lin , amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org References: <20251126065126.54016-1-iam@lach.pw> <20251126065126.54016-3-iam@lach.pw> <68c55e772424f8e001898cdd1edcf4856820461e@intel.com> <41fbf5af-559a-4810-82c1-5c2e8a497e5b@0la.ch> <493bcd10bdfc8a3123323b77eead3dacadc08e3c@intel.com> <2f847ef3-9fb9-46a1-b5bd-38d8498b7772@0la.ch> Content-Language: en-US From: Yaroslav In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2025-11-26 15:47, Jani Nikula wrote: > On Wed, 26 Nov 2025, Yaroslav wrote: >> On 2025-11-26 15:29, Jani Nikula wrote: >>> On Wed, 26 Nov 2025, Yaroslav 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. > >