Lines Matching full:buffers
27 <p>Having buffers of graphical data is wonderful, but life is even better when
34 <p>SurfaceFlinger's role is to accept buffers of data from multiple sources,
68 the screen only once per refresh cycle, submitting buffers for display at 200fps
74 layers looking for new buffers. If it finds a new one, it acquires it; if not,
76 to have something to display, so it will hang on to one buffer. If no buffers
79 <p>After SurfaceFlinger has collected all buffers for visible layers, it asks
86 way to composite buffers with the available hardware. As a HAL, its
90 planes</em>, the purpose of which is to composite multiple buffers together in
94 are in separate buffers. You could handle composition using either of the
101 <li>Passing all three buffers to the display hardware and tell it to read data
102 from different buffers for different parts of the screen.</li>
128 set of buffers, the HWC can continue to show the previously-composited scratch
164 (mediaserver) so we have to move large graphics buffers around the system. To
168 <p>The MediaCodec class allows an app to provide data as raw bytes in buffers,
177 SurfaceFlinger is the producer of buffers rather than the consumer.</p>
180 appear. As apps draw, their buffers travel to SurfaceFlinger, which composites
183 Internally, mediaserver has its own way of moving buffers around that also
