summaryrefslogtreecommitdiffstats
path: root/minuitwrp/graphics.cpp (unfollow)
Commit message (Collapse)AuthorFilesLines
2017-01-21ifdef overlay graphicsEthan Yonker1-3/+5
Change-Id: If3173ddbfaccb95cc48636240ee3a918dac1e23f
2016-04-28Restore TW_SCREEN_BLANK_ON_BOOT functionality.¨Paul1-0/+6
This is required for a number of devices, particularly now that custom graphics support is deprecated. This change is required to officially support TWRP on the Huawei Plank (aka the Honor 7). Change-Id: Ie16ec557c75654c9c9e7a2877aee3339fc214d05
2016-01-27Update minuitwrp graphics in line with latest minuiEthan Yonker1-0/+416
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