linux-kernel - Re: [PATCH v4 12/12] arm64: dts: qcom: sdm845-lg-common: remove framebuffer reserved-mem

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <88d96898-3c83-438d-89e9-4bb2bd0dd98b@ixit.cz>
Date: Wed, 3 Dec 2025 11:45:06 +0100
From: David Heidelberg <david@...t.cz>
To: Paul Sajna <sajattack@...tmarketos.org>,
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, phone-devel@...r.kernel.org,
 Amir Dahan <system64fumo@...tonmail.com>,
 Christopher Brown <crispybrown@...il.com>
Subject: Re: [PATCH v4 12/12] arm64: dts: qcom: sdm845-lg-common: remove
 framebuffer reserved-mem

On 03/12/2025 11:37, David Heidelberg wrote:
> On 03/12/2025 09:42, Paul Sajna wrote:
>> December 2, 2025 at 10:34 AM, "Konrad Dybcio" 
>> <konrad.dybcio@....qualcomm.com mailto:konrad.dybcio@....qualcomm.com? 
>> to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > 
>> wrote:
>>
>>
>>>
>>> On 12/2/25 5:41 AM, Paul Sajna wrote:
>>>
>>>>
>>>> December 1, 2025 at 12:41 PM, "Konrad Dybcio" 
>>>> <konrad.dybcio@....qualcomm.com 
>>>> mailto:konrad.dybcio@....qualcomm.com? 
>>>> to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > 
>>>> wrote:
>>>>
>>>>>
>>>>> On 11/25/25 9:12 AM, Paul Sajna wrote:
>>>>>
>>>>   It causes this warning
>>>>   [ 0.000000] OF: reserved mem: OVERLAP DETECTED!
>>>>   framebuffer@...00000 mailto:framebuffer@...00000
>>>>   (0x000000009d400000--0x000000009f800000) overlaps with
>>>>   memory@...00000 mailto:memory@...00000 
>>>> (0x000000009d400000--0x000000009f800000)
>>>>   Signed-off-by: Paul Sajna <sajattack@...tmarketos.org>
>>>>   ---
>>>>
>>>>>
>>>>> It's defined for both devices that include this dtsi.. perhaps you
>>>>>   could remove it from there
>>>>>
>>>>>   Konrad
>>>>>
>>>>   I don't have a judyp to test with and prefer to limit scope.
>>>>
>>> This is a mechanical change
>>>
>>> Konrad
>>>
>>
>> Sorry, I tried to have a look at what you meant but didn't quite 
>> understand. In this patch I changed the dtsi that is included by both 
>> already. I don't see any other reserved-mem nodes in judyp. Do you 
>> mean I should remove the framebuffer from judyp? I don't think that's 
>> wise since a panel driver isn't added as far as I know.
> 
> I think this warning likely comes from sdm845-mainline repo, as it has 
> extra patches, which trying to abstract framebuffer into sdm845.dtsi, 
> where it likely conflicts, have you tried against clean 6.18-rcX or next?

... or sdm845-next repo [1]?

I sent the patches moving framebuffer from sdm845-mainline repository as 
RFC [2], but so far it's not clear to me if these should go in or not.

David

[1] https://gitlab.com/sdm845/sdm845-next/-/commits/sdm845-next
[2] 
https://lore.kernel.org/all/20251117-commonize-framebuffer-v1-1-e4c099b383c9@ixit.cz/

> 
> David

-- 
David Heidelberg