108e84f7e6a9117b66dba000dcf16c6d8c862e16 |
|
08-May-2017 |
Hendrik Wagenaar <hendrikw@google.com> |
dvrapi: Pass layer_count down * We were missing layer count, which would prevent multiview from working Bug: 37245304 Test: MultiLayerBufferQueue Change-Id: I88b41f1aa7665df01e89a7386cbc23b15c9a79b0
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
044963e1dd0479035b6e5f2c6bd618bde7143710 |
|
02-May-2017 |
Jiwen 'Steve' Cai <jwcai@google.com> |
Deprecate producer/consumer usage: Step 1 Clean up producer/consumer usage from IonBuffer. Bug: 37881101 Test: Build, flash, ran particles.apk Change-Id: I66a8c4db2348b014a7b458b69157ed7c150112e1
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
73feb0676635da6c0f738c10e04052a8162a4095 |
|
20-Apr-2017 |
Chris Forbes <chrisforbes@google.com> |
vr: Adjust for libui gralloc flags change Change-Id: I24dbe407ad9139ba1d206b9074c7c507537d198c Bug: b/33350696 Test: Bullhead: booted to launcher, take photo, watch youtube
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
cd52dd9f1b301854b4e1734e3741d9cef8f784b1 |
|
08-Apr-2017 |
Corey Tabaka <eieio@google.com> |
Update BufferHub service/client with support for gralloc1 usage. - Add support for gralloc1 usage flags. - Mimic how GraphicBuffer supports gralloc0 usage flags: (usage, usage). - Move to using pdx::Status<T> since we're touching signatures everywhere. Bug: 36401174 Test: bufferhub_tests; buffer_hub_queue-test Change-Id: I0e5184197b21eda9806bbea44f63b546b030692a
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
b42f171a5a76985fde2689d90fd6d2d7e4920564 |
|
21-Mar-2017 |
Chia-I Wu <olv@google.com> |
libui: clean up GraphicBuffer interface Other than transferring the ownership, some callers want to control whether to register or to clone the handle when creating a GraphicBuffer from a handle. Add a new constructor with HandleWrapMethod for finer controls, to replace the one that has only a boolean, keepOwnership. The motivation is to enable users to construct GraphicBuffer without fighting with GraphicBufferMapper::registerBuffer first. More generally, GraphicBufferMapper::{registerBuffer,unregisterBuffer} is tricky to use correctly. They should really be considered private by most. While at it, deprecate constructors that do not distinguish producer/consumer usage. It turns out GraphicBuffer is used by some proprietary libraries. I have to maintain the ABI and cannot remove the deprecated constructors. Bug: 36355756 Test: boots Change-Id: Ieea618d8495f06a6233299d076fb821127cd6bf8
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
8a71b13127f737a46c55ba94d31ba0262e7cbf8a |
|
16-Mar-2017 |
Mark Urbanus <urbanus@google.com> |
Refactor IonBuffer to use GraphicBuffer - Replace gralloc0 based implementation with GraphicBuffer implementation. - Removed incompatible ion-buffer unit-tests. - Added libui dependencies to dependants. Bug: 34879523 Test: Tested on Lucid, validated graphics and poses are working Change-Id: I49a129f269d54c81bda93b44d879d4b8dee2006a
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
4fe60582f314e381098f8f3bc2e39c5880e9243a |
|
02-Feb-2017 |
Alex Vakulenko <avakulenko@google.com> |
Remove references to libchrome Removed dependencies on libchrome which was used mostly for logging and switched over to standard Android log macros. Bug: None Test: `m -j32` still succeeds Change-Id: I0a841c19c15c02f9a031af200e82837f9450d88a
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|
e4eec20f6263f4a42ae462456f60ea6c4518bb0a |
|
27-Jan-2017 |
Alex Vakulenko <avakulenko@google.com> |
Add DaydreamVR native libraries and services Upstreaming the main VR system components from master-dreamos-dev into goog/master. Bug: None Test: `m -j32` succeeds. Sailfish boots and basic_vr sample app works Change-Id: I853015872afc443aecee10411ef2d6b79184d051
/frameworks/native/libs/vr/libbufferhub/ion_buffer.cpp
|