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 32A7C303A26 for ; Wed, 26 Nov 2025 14:41:11 +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=1764168074; cv=none; b=XPSYdaUgPUlwycOVk05Ba0v5nY5yxGrD+OpT0gquXwv2hKa/cWyBYhYtvVpJ55FgzHxa6cUDUQ5jXvq9HRpEbQ6qZRq6EwxztwsLbimfI386M9MuOBHVFHf1Z7yPtZ7Afogr1aGKXcCqni78mp8HHB5qJT3BK4CsyQ1gXkHD4yw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764168074; c=relaxed/simple; bh=zEQwFyoFQJT50SOfvCJFXLevpWk09Zh7RMBe4j2FGrs=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Or6GiyNPIkEjkxG0HNqdkt2ywHWcMN5nWx4V5ffwkQbXIRd0cig/8rZdEFe9nLnXQfWm6G1SVfKezhYHnLAyhwkFzN8GuBmZ1tTkt/1s1djwe0YKRhz2VWCHsKHIv2ENBRKVuI+JidH8cdgkZ1/zlFE5FJPVQDohZwSr3ODtp6o= 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=n1RqwyqC; dkim=permerror (0-bit key) header.d=0la.ch header.i=@0la.ch header.b=3kTyR2ih; 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="n1RqwyqC"; dkim=permerror (0-bit key) header.d=0la.ch header.i=@0la.ch header.b="3kTyR2ih" DKIM-Signature: v=1; a=rsa-sha256; s=202502r; d=0la.ch; c=relaxed/relaxed; h=From:To:Subject:Date:Message-ID; t=1764168069; bh=SbtXzmhcC0yTTttgmIST0I9 9SrvnQllmE8i9G90uEsk=; b=n1RqwyqCdzxMBQqcNn4FwZN4JUMD2bTfxjqNxWixJ2b4AxZUyV 8TXukpowX0SmcxFwkx6wSoWtZJ5wL25BcunvDMWr38iwuQIcU1nEvRCtWccJbNtGIGClWzQXp8L Jj6CWI/D2GtfDVSo+IpX8ZExB/9Tu9Bq7dmCmm/fRsdgSN8pqKip8lTA6uLO+5xDPDi3Z9dlJIp 9IAlaQ4jwmGNWu7eRO80z4HKZnu1ArnBoiKU1nhmTG9661ch8+E18QPcPMOQkG999BnimPDW45i ha3E/Ul0F1ZGQd49o93P/2ywPQrKmg8MkfRIcwp/Orz80cENJ5OrwJ++DO4qE1RSj/w==; DKIM-Signature: v=1; a=ed25519-sha256; s=202502e; d=0la.ch; c=relaxed/relaxed; h=From:To:Subject:Date:Message-ID; t=1764168069; bh=SbtXzmhcC0yTTttgmIST0I9 9SrvnQllmE8i9G90uEsk=; b=3kTyR2ihMCY/GE3U5T9QfbFORAC0ltcHS6fCUjWKbIkvq+kPTc sWJQ0vDT4z1ZJFJwEfw73mmsPlL9FerqTnDA==; Message-ID: <2f847ef3-9fb9-46a1-b5bd-38d8498b7772@0la.ch> Date: Wed, 26 Nov 2025 15:41:08 +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> Content-Language: en-US From: Yaroslav In-Reply-To: <493bcd10bdfc8a3123323b77eead3dacadc08e3c@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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. > BR, > Jani. > >