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: <6af504ef-55b8-4599-a379-40842edfcfa5@kernel.org>
Date: Thu, 3 Jul 2025 11:45:57 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Maxime Ripard <mripard@...nel.org>, Hans de Goede <hdegoede@...hat.com>
Cc: Thomas Zimmermann <tzimmermann@...e.de>,
 Luca Weiss <luca.weiss@...rphone.com>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
 David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>,
 Javier Martinez Canillas <javierm@...hat.com>, Helge Deller <deller@....de>,
 linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: display: simple-framebuffer: Add
 interconnects property

On 03/07/2025 11:41, Maxime Ripard wrote:
>>> But does that work with *any* device that requires interconnects? The next such simple-framebuffer device should work out of the box *without* the kernel knowing anything about it. That's one of the key features of the simple-framebuffer.  If we have to maintainer per-device feature sets, it breaks that assumption.
>>
>> The driver code for this can still be generic and since the driver
>> will bind to the fallback plain "simple-framebuffer" compatible
>> this should also work for new platforms.
>>
>> The e.g. "qcom.simple-framebuffer-sm8650-mdss" compatible would
>> purely be something in the dt-bindings to document which simplefb
>> implementations will have interconnects and which ones will not.
>>
>> The driver does not necessarily need to check these more
>> precise compatibles, it can still just check for the generic
>> presence of interconnects.
> 
> This ship has kind of sailed though. This binding has been used by
> plenty of firmwares and bootloaders over the years, and has been
> deployed on plenty of devices already.
> 
> Good luck fixing it in all of them, and then updating every device.
No one suggested that... We speak about new devices, although maybe this
one SM7635 new device runs plenty of firmwares and bootloaders?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ