summaryrefslogtreecommitdiffstats
path: root/minuitwrp/graphics_drm.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* libminuitwrp updates for Pixel 3 devicesEthan Yonker2019-01-161-2/+2
| | | | | | | | | Fix rules for adf graphics to detect their presence when ninja make files are used. Change pixelflinger graphics mode so that colors display properly on the Pixel 3 Change-Id: Ie7181be6c5e1e9a007b58fd798b2cef787ce4a01
* Revert "minuitwrp: drm: wait for last page flip to complete"Simon Shi2018-06-051-20/+1
| | | | | | | | See https://github.com/omnirom/android_bootable_recovery/issues/219 This reverts commit 34ad728823b186f93016387f39388cdbde35b3ed. Change-Id: Ia659b49af8206ba74b098aa721099a180762bab5
* minuitwrp: drm: wait for last page flip to completeSimon Shields2018-05-251-1/+20
| | | | | | | | if we try and flip pages too quickly, the kernel returns -EBUSY. Use drmHandleEvent to wait for any previous flip to complete before attempting a new one. Change-Id: If3def889c0c89d7cfb8b7f13c4dae6d4b12760f9
* minuitwrp: use a separate draw buffer for DRM as wellSimon Shields2018-05-251-2/+28
| | | | | | | | draw performance is significantly slower when drawing directly to the mmaped buffer. Instead, draw to a userspace buffer and memcpy() to the mmaped buffer on page flip. Change-Id: Ibf2cd4be4f5437b445e68c572ff76ad72d506b15
* minuitwrp: drm: fix RECOVERY_BGRA pixel formatSimon Shields2018-05-251-2/+2
| | | | | | GGL_PIXEL_FORMAT_RGBA8888 seems to work in this instance. Change-Id: I88fb3e53332f47952036ef6e617b3ea7d0b639a9
* Update minuitwrp graphics in line with latest minuiEthan Yonker2016-01-271-0/+492
Note: events.cpp is still old code renamed to cpp to make it easier to call functions like gr_fb_width(). I had to modify AOSP fbdev code to provide a separate memory surface for drawing to as drawing directly to the framebuffer resulted in rendering taking about 5 times longer. I also modified AOSP adf code to provide a separate memory surface for drawing for the same performance reasons. The Nexus 9 supports adf graphics. Overlay graphics work on at least one device. Overlay provides a separate memory buffer already so performance is good. I do not have a drm device yet that I know of. I made some attempt to update the drm code to determine the correct pixel format based on the drm graphics format, but what is available in pixel flinger and what is available in drm do not line up all that well. Reports are that the Pixel C is using drm graphics, but performance is slow, likely due to the use of a mmap instead of a memory buffyer. Change-Id: Ibd45bccca6ac2cb826037aa9b2aa5065cf683eed