[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d46f0ad4-4319-496f-9093-54bb5a000875@oss.qualcomm.com>
Date: Fri, 20 Dec 2024 22:13:55 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Pengyu Luo <mitltlatltl@...il.com>, andersson@...nel.org,
conor+dt@...nel.org, konradybcio@...nel.org, krzk+dt@...nel.org,
robh@...nel.org
Cc: chenxuecong2009@...look.com, devicetree@...r.kernel.org, gty0622@...il.com,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: sc8280xp: Add Huawei Matebook E
Go (sc8280xp)
On 20.12.2024 5:05 PM, Pengyu Luo wrote:
> Add an initial devicetree for the Huawei Matebook E Go, which is based on
> sc8280xp.
>
> There are 3 variants, Huawei released first 2 at the same time.
> Huawei Matebook E Go LTE(sc8180x), codename should be gaokun2.
> Huawei Matebook E Go(sc8280xp@...GHz), codename is gaokun3.
> Huawei Matebook E Go 2023(sc8280xp@...9GHz).
>
> We add support for the latter two variants.
>
> This work started by Tianyu Gao and Xuecong Chen, they made the
> devicetree based on existing work(i.e. the Lenovo X13s and the
> Qualcomm CRD), it can boot with framebuffer.
>
So this looks good now, but
[...]
> + chosen {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + framebuffer0: framebuffer@...00000 {
> + compatible = "simple-framebuffer";
> + reg = <0x0 0xc6200000 0x0 0x02400000>;
> + width = <1600>;
> + height = <2560>;
> + stride = <(1600 * 4)>;
> + format = "a8r8g8b8";
> + };
> + };
I still don't understand why efifb doesn't work for you.
Could you share your .config file?
Konrad
Powered by blists - more mailing lists