Hi, On Fri, 17 Dec 2021 at 15:58, Felipe Balbi <balbi@xxxxxxxxxx> wrote: > > From: Felipe Balbi <felipe.balbi@xxxxxxxxxxxxx> > > Hi folks, > > I'm trying to enable the framebuffer on Microsoft Surface Duo. Looking > through some internal docs, it came to my attention that the bootloader > will fill up the framebuffer address and size to a memory node names > splash_region. Adding the node, I can see the address of the > framebuffer. Creating the relevant framebuffer device using > simple-framebuffer, I can't see it working. Tried dd if=/dev/urandom > of=/dev/fb0 and fb-test. None of which manage to get rid of what's > already on the screen, put there by the bootloader (platform Logo). > > Wondering if any of you have seen a behavior such as this and how did > you manage to get framebuffer working on SM8150 (I see at least Sony > Xperia has the node). What issues do you have with the DRM_MSM/DPU1 driver? I think it supports 8150. > > Felipe Balbi (2): > arm64: boot: dts: qcom: sm8150: add a label for reserved-memory > arm64: boot: dts: qcom: surface duo: add minimal framebuffer > > .../dts/qcom/sm8150-microsoft-surface-duo.dts | 19 +++++++++++++++++++ > arch/arm64/boot/dts/qcom/sm8150.dtsi | 2 +- > 2 files changed, 20 insertions(+), 1 deletion(-) > > -- > 2.34.1 -- With best wishes Dmitry
