Jamie Gennis dd3cb84cfb SurfaceFlinger: add support for secure displays ... This change adds support for displays that are not allowed to display surfaces with the eSecure flag set. All non-virtual displays are considered secure, while virtual displays have their secure-ness specified at creation time. Bug: 7368436 Change-Id: I81ad535d2d1e5a7ff78269017e85b111f0098500		2012-10-22 13:41:21 -07:00
..
tests
Android.mk
BitTube.cpp
BufferItemConsumer.cpp	Fix race condition in ConsumerBase::addReleaseFence()	2012-10-05 14:40:50 -07:00
BufferQueue.cpp	BufferQueue: alloc without holding the lock	2012-10-11 20:08:26 -07:00
CleanSpec.mk
ConsumerBase.cpp	Fix race condition in ConsumerBase::addReleaseFence()	2012-10-05 14:40:50 -07:00
CpuConsumer.cpp
DisplayEventReceiver.cpp
DummyConsumer.cpp
GuiConfig.cpp
IDisplayEventConnection.cpp
IGraphicBufferAlloc.cpp
ISensorEventConnection.cpp
ISensorServer.cpp
ISurface.cpp
ISurfaceComposer.cpp	SurfaceFlinger: add support for secure displays	2012-10-22 13:41:21 -07:00
ISurfaceComposerClient.cpp
ISurfaceTexture.cpp
LayerState.cpp
Sensor.cpp
SensorEventQueue.cpp
SensorManager.cpp
Surface.cpp
SurfaceComposerClient.cpp	SurfaceFlinger: add support for secure displays	2012-10-22 13:41:21 -07:00
SurfaceTexture.cpp	Fix race condition in ConsumerBase::addReleaseFence()	2012-10-05 14:40:50 -07:00
SurfaceTextureClient.cpp