On Tue, Sep 15, 2020 at 3:10 AM Peter Collingbourne <pcc@xxxxxxxxxx> wrote: > On Tue, Jun 9, 2020 at 1:08 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > > > > All the functionality in this driver has been reimplemented > > in the new DRM driver in drivers/gpu/drm/pl111/* and all > > the boards using it have been migrated to use the DRM driver > > with all configuration coming from the device tree. > > Android's FVP configuration still uses FBDEV. But all DRM drivers support frame buffer emulation so I don't see how this can be a problem? The new DRM driver provides a framebuffer. I'm also confused about how this can be in use. fvp-base-revc.dts includes rtsm_ve-motherboard.dtsi where the PL111 is defined. commit f1fe12c8bf33241e04c57a0fc5b25b16ba77ba2d "ARM: dts: Modernize the Vexpress PL111 integration" changes the DTS for the FVP such that only the new DRM driver really works with it: it removes the panel-dpi encoded panel and defines the panel "arm,rtsm-display" for FVP and that is *only* supported by drivers/gpu/drm/panel/panel-simple.c from DRM. The upstream FVP has been using the new DRM driver by default since commit 37ad688497785c9ad1471236e28efda1e2f39741 "arm64: defconfig: Switch to PL11x DRM driver" in january 2019. Are you using old or outoftree devicetrees with a newer kernel? > While it would be great > to see it migrated to DRM, this first requires resolving a design > incompatibility between Android's composer and DRM devices that only > support software rendering. I proposed a patch that would help resolve > this [1], but there was disagreement about the approach and I haven't > had time to get back to this. > > Can this please be reverted until FVP on Android can be migrated to DRM? We need a clear technical reason, I understand that using DRM directly might be a problem, but DRM supports full framebuffer emulation and from a userspace point of view, what the new driver provides should be equivalent. I can think of problems like Android seeing the new fancy DRM userspace ABI but surely it can be instructed to ignore that and just use the framebuffer emulation instead? If there is anything else making DRMs framebuffer emulation substandard I am sure the DRM developers would like to know, especially if it makes Android unhappy. Yours, Linus Walleij _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
