I don't suppose you could send a libdrm patch to the list with an up to date version of the g2dtest code so we can get it in libdrm tree? BR, -R On Fri, Mar 16, 2012 at 1:28 AM, Joonyoung Shim <jy0922.shim@xxxxxxxxxxx> wrote: > On 03/15/2012 07:50 PM, Dave Airlie wrote: >>> >>> G2D is a 2D graphic accelerator that supports Bit Block Transfer. This >>> G2D driver is exynos drm specific and supports only exynos4x12 series. >>> user application fills command set in cmdlist and once dma start request >>> these cmdlists are parsed and performed by dma. >> >> Where is this block documented or a pointer to the corresponding open >> userspace user code? > > > I attach simple g2dtest program patch. The base of this patch is master > branch of lastest libdrm git. > > This user progrem can test just solid color fill example. > I will cleanup and update it for more operations later. > > Thanks. > > >> Again the ioctls look like they need to be depointered and use __u64. >> >> It would be nice if you could document how the command stream and engine >> work. >> >> How does userspace pass addresses to it? straight or via gem objects? >> how does it >> stop userspace blt to places it shouldn't etc. >> >> I'm getting the feeling this accel enabled driver needs a lot more of >> a commit message >> and lot more documentation on what it can be used for. >> >> Dave. >> _______________________________________________ >> dri-devel mailing list >> dri-devel@xxxxxxxxxxxxxxxxxxxxx >> http://lists.freedesktop.org/mailman/listinfo/dri-devel >> > > > _______________________________________________ > dri-devel mailing list > dri-devel@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/dri-devel > _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
