| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
* Required for devices like Sony Huashan (dual backlighting paths)
Change-Id: I0f84623431aec91fafee6617c1d4c542e4566caf
|
| |
|
|
|
|
|
| |
The driver already has the capability to do so.
It needs only to be flagged, if required.
Change-Id: I1d81b00a7499e493d1dbba0a440b45fc1202f7c1
|
| |
|
|
| |
Change-Id: I436bab6ef679168d3625d8e1837917077cf89908
|
|
|
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
|
