replicant-frameworks_native/services/surfaceflinger
Jesse Hall ffe1f19ca9 Fix virtual displays for HWC<=1.1
If we're using a HWC that doesn't support virtual displays, or we have
more virtual displays than HWC supports concurrently, the
VirtualDisplaySurface should simply be a passthrough from source
(GLES) to sink.

This change also tries to distinguish between display types and HWC
display IDs a little better, though there's more to do here. Probably
needs a higher-level rethink; it's too error-prone now.

Bug: 8446838
Change-Id: I708d2cf262ec30177042304f174ca5b8da701df1
2013-03-22 15:27:58 -07:00
..
DisplayHardware Fix virtual displays for HWC<=1.1 2013-03-22 15:27:58 -07:00
tests
Android.mk
Barrier.h
Client.cpp
Client.h
clz.cpp
clz.h
DdmConnection.cpp
DdmConnection.h
DisplayDevice.cpp Fix virtual displays for HWC<=1.1 2013-03-22 15:27:58 -07:00
DisplayDevice.h Fix virtual displays for HWC<=1.1 2013-03-22 15:27:58 -07:00
EventThread.cpp
EventThread.h
FrameTracker.cpp
FrameTracker.h
GLExtensions.cpp
GLExtensions.h
Layer.cpp
Layer.h
LayerDim.cpp
LayerDim.h
MessageQueue.cpp
MessageQueue.h
MODULE_LICENSE_APACHE2
SurfaceFlinger.cpp Fix virtual displays for HWC<=1.1 2013-03-22 15:27:58 -07:00
SurfaceFlinger.h
SurfaceFlingerConsumer.cpp
SurfaceFlingerConsumer.h
SurfaceTextureLayer.cpp
SurfaceTextureLayer.h
Transform.cpp
Transform.h