On Wed, Apr 15, 2020 at 02:41:52PM +0200, H. Nikolaus Schaller wrote: > Hi Maxime, > > > Am 15.04.2020 um 12:10 schrieb Maxime Ripard <maxime@xxxxxxxxxx>: > > > > Hi, > > > > On Wed, Apr 15, 2020 at 10:35:07AM +0200, H. Nikolaus Schaller wrote: > >> * rebased to v5.7-rc1 > >> * added DTS for for a31, a31s, a83t - by Philipp Rossak <embed3d@xxxxxxxxx> > >> * added DTS for "samsung,s5pv210-sgx540-120" - by Jonathan Bakker <xc-racer2@xxxxxxx> > >> * bindings.yaml fixes: > >> - added a31, a31 > >> - fixes for omap4470 > >> - jz4780 contains an sgx540-130 and not -120 > >> - a83t contains an sgx544-115 and not -116 > >> - removed "additionalProperties: false" because some SoC may need additional properties > >> > >> PATCH V5 2020-03-29 19:38:32: > >> * reworked YAML bindings to pass dt_binding_check and be better grouped > >> * rename all nodes to "gpu: gpu@<address>" > >> * removed "img,sgx5" from example - suggested by Rob Herring <robh+dt@xxxxxxxxxx> > >> > >> PATCH V4 2019-12-17 19:02:11: > >> * MIPS: DTS: jz4780: removed "img,sgx5" from bindings > >> * YAML bindings: updated according to suggestions by Rob Herring > >> * MIPS: DTS: jz4780: insert-sorted gpu node by register address - suggested by Paul Cercueil > >> > >> PATCH V3 2019-11-24 12:40:33: > >> * reworked YAML format with help by Rob Herring > >> * removed .txt binding document > >> * change compatible "ti,am335x-sgx" to "ti,am3352-sgx" - suggested by Tony Lindgren > >> > >> PATCH V2 2019-11-07 12:06:17: > >> * tried to convert bindings to YAML format - suggested by Rob Herring > >> * added JZ4780 DTS node (proven to load the driver) > >> * removed timer and img,cores properties until we know we really need them - suggested by Rob Herring > >> > >> PATCH V1 2019-10-18 20:46:35: > >> > >> This patch series defines child nodes for the SGX5xx interface inside > >> different SoC so that a driver can be found and probed by the > >> compatible strings and can retrieve information about the SGX revision > >> that is included in a specific SoC. It also defines the interrupt number > >> to be used by the SGX driver. > >> > >> There is currently no mainline driver for these GPUs, but a project > >> [1] is ongoing with the goal to get the open-source part as provided > >> by TI/IMG and others into drivers/gpu/drm/pvrsgx. > > > > Just a heads up, DRM requires an open-source user-space, so if your > > plan is to move the open-source kernel driver while using the > > closed-source library (as that page seem to suggest), that might > > change a few things. > > The far future goal is to arrive at a completely open implementation, > but nobody knows how to get there. Therefore we bake smaller bread :) > > step 1: get SoC integration right and stable (this is what this series is for) > step 2: make the open source kernel driver work with closed-source libs > step 3: write open-source replacements for user-space step4: clean up the kernel driver step5: get the mesa driver and kernel driver reviewed step6: get it all merged It's a very long road, but awesome to hear that someone is taking care of pvrsgx. And I'm totally fine with landing stuff like you propose in step 1. Just not the driver/uapi itself. Goog luck and have fun! Cheers, Daniel > > > > >> The kernel modules built from this project have successfully > >> demonstrated to work with the DTS definitions from this patch set on > >> AM335x BeagleBone Black, DM3730 and OMAP5 Pyra and Droid 4. They > >> partially work on OMAP3530 and PandaBoard ES but that is likely a > >> problem in the kernel driver or the (non-free) user-space libraries > >> and binaries. > >> > >> Wotk for JZ4780 (CI20 board) is in progress and there is potential > >> to extend this work to e.g. BananaPi-M3 (A83) and some Intel Poulsbo > >> and CedarView devices. > > > > If it's not been tested on any Allwinner board yet, I'll leave it > > aside until it's been properly shown to work. > > Phillip has testes something on a83. > > BR and thanks, > Nikolaus -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
