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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1d56eccf-1978-43c2-afcf-03ca88acc0e2@oss.qualcomm.com>
Date: Tue, 2 Dec 2025 11:34:37 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Paul Sajna <sajattack@...tmarketos.org>,
        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>, David Heidelberg <david@...t.cz>
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 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