linux-kernel - Re: [RFC/patch 2/2] arm64: boot: dts: qcom: surface duo: add minimal framebuffer

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>] [day] [month] [year] [list]

Message-ID: <87lf0i4c2l.fsf@kernel.org>
Date:   Sat, 18 Dec 2021 09:15:30 +0200
From:   Felipe Balbi <balbi@...nel.org>
To:     Alexey Minnekhanov <alexeymin@...tmarketos.org>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC/patch 2/2] arm64: boot: dts: qcom: surface duo: add
 minimal framebuffer


Hi,

Alexey Minnekhanov <alexeymin@...tmarketos.org> writes:
> @@ -472,6 +483,14 @@ &pon_resin {
>  	linux,code = <KEY_VOLUMEDOWN>;
>  };
>  
> +&reserved_memory {
> +	splash_region: splash_region@...00000 {
> +		/* We expect the bootloader to fill in the size */
> +		reg = <0x0 0x9c000000 0x0 0x0>;
>
> 0x2400000 should be here as size, maybe?

bootloader is filling that up, but sure I only used this to get the size
and base address from bootloader. I could just hardcode the values now
that I know them :-)

>
> 	 cont_splash_mem: memory@...00000 {
> 		reg = <0x0 0x9c000000 0x0 0x2400000>;
> 		no-map;
> 	};
>
> FWIW, example above (with similar simple-framebuffer
> node) worked fine for my sm8150 based device.

Oh okay. So it's likely to be something specific to our bootloader.

-- 
balbi