| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
libcameraservice: Stop using IGBC::BufferItem
(cherry picked from commit 027c772ed30ddd32808df669e37a53e9b97b1f99)
libstagefright: Stop using IGBC::BufferItem
(cherry picked from commit 983e2be81f9ea767ae4d8b19669c1c080ecf58d4)
|
|
|
|
|
|
|
|
| |
Passes the BufferItem for the queued buffer to the onFrameAvailable
callback so the consumer can track the BufferQueue's contents.
Bug: 18111837
Change-Id: If9d07229c9b586c668e5f99074e9b63b0468feb0
|
|
|
|
|
|
|
|
| |
After ZSL queue is cleared, don't add capture result to ZSL queue
if its corresponding buffer has been cleared.
Bug: 17185356
Change-Id: Iddac39ab09b2560e2ce9390895927217c1736d5a
|
|\
| |
| |
| |
| |
| |
| |
| | |
klp-modular-dev-plus-aosp
* commit '5c679d41714e42f153f6aeb492df54510a195bc1':
libcameraservice: build 64-bit
libcameraservice: fix 64-bit print format warnings
|
| |
| |
| |
| |
| |
| |
| | |
Use PRId64 from inttypes.h to print nsecs_t (int64_t)
Use %zu to print size_t
Change-Id: I135620e0388db33587a8a7da393b48a45cb7275a
|
|\ \
| |/
| |
| |
| |
| |
| | |
ISO C++11 mode"
* commit 'a2949165680158db31dc1fce32f62bbe70c31820':
libcameraservice: Fix build in ISO C++11 mode
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change log macro define so it can't be confused for a C++11 string
literal
Change-Id: Idcc8085735177aa3313fdea66dc0736cca749f9b
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
|
|/ /
| |
| |
| | |
Change-Id: I4730ac7849e915e88d3b8fc8aa869f53a8242501
|
| |
| |
| |
| |
| | |
Bug: 9265647
Change-Id: Iefabc11e4bd2e2e8ffd31160476c450affe6629c
|
| |
| |
| |
| | |
Change-Id: I3c5d4be2a2e8783fbf98b3e268fd02658f71dc7d
|
| |
| |
| |
| |
| |
| | |
Bug 7900302
Change-Id: I30b9cca783e0a48f77035b745b7d5e20edf10f27
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Update BufferQueue and ConsumerBase users to new BufferQueue
API, to allow BufferQueue slots to be reused. Buffer consumers
generally now need to track the unique frameNumber belonging to
each frame acquired if they are using BufferQueue directly.
Otherwise, they can simply track the graphicBuffer.
Change-Id: I30ee3158cf40fb10bbd085241646d5f1128ee480
Signed-off-by: Lajos Molnar <lajos@google.com>
Related-to-bug: 7093648
|
|
|
|
|
| |
Bug: 9007356
Change-Id: I0ced31020410978c549d408b2815f925e9c9ffcf
|
|
|
|
|
| |
Bug: 8988871
Change-Id: I24a2620d356f3bb6207ed834c79fd3e48b429695
|
|
|
|
|
| |
Bug: 8969579
Change-Id: Ia51d4072725754fd3b6ca028232a605885376287
|
|
Bug: 8563838
Change-Id: I5a95e0be94e5388b30639905efae42d3c3279f72
|