History log of /frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4f3895ce61663a8de76bd69a574381b31c8bb28e 05-Dec-2017 Chih-Hung Hsieh <chh@google.com> Fix clang compiler warnings.

* Do not include <base/logging.h> to avoid redefinition warnings.
* Use unsigned 0U to avoid signed vs unsigned comparison.
* Fix typo of unused ret2.

Bug: 66996870
Test: build with WITH_TIDY=1
Change-Id: I5554ffaadd54d967580998672e1dd64428269566
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
99c2d73588dad4a4d12a17d37354237b8c11a16a 08-Jun-2017 Corey Tabaka <eieio@google.com> Move global buffer ops to VR display service.

The original home for these ops was the VR display manager service,
which is a protected singleton service that may only have one client.
Since more than one service needs to create global buffers, move these
ops to the display service. They are already protected by permission
checks.

Bug: 62424911
Test: dvr_api-test passes
Change-Id: Ia2f57fdf8a5258b52a652935d160e90db0f1cf9e
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
6f468c6a3731d2bae41c4b86143b7246fcde1f83 31-May-2017 Okan Arikan <okana@google.com> Sync up the DvrConfig struct with Google3

Bug: 38506720
Test: No functional change. Just make.
Change-Id: Ib159dd156cef353a7881bc6b4004c46da5e2d449
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
822b710a714c342dda0087f594c8ababa6630f44 08-May-2017 Okan Arikan <okana@google.com> Adopt the use of shared buffers.

Bug: 37001948
Test: Make system image
Change-Id: I032574f250e0f0fe7768af649730406e24d853db
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
954796e27e89209b38b35779949c243bec490c28 11-May-2017 John Bates <jbates@google.com> Add shmem config buffer to libvrflinger

This allows VrCore to configure some tunable behaviors
of libvrflinger.

- Added dvrDisplayManagerDeleteNamedBuffer for testing config buffer
creation.
- Added tests for named buffers, including one for the config buffer.
- Added IsValid to broadcast_ring to avoid tracking redundant state
externally.

Bug: 38193993
Test: Run dvr_named_buffer-test
Change-Id: I52722dd314233b5bea1ca6377c14b5c856825746
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
36d23803882c64b1006cd3b8a47e00a4193a9b49 16-May-2017 Okan Arikan <okana@google.com> Int key for the named buffers.

Also, rename them to global buffers from named buffers.

Bug: 38320428
Test: Run frameworks/native/libs/vr/libdvr/tests on device
Change-Id: I2109aea77e35f2ccd8055208058df4b7287c1d5e
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
2251d822dac2a96aad4184a6fdc2690f0a58af7c 21-Apr-2017 Corey Tabaka <eieio@google.com> Remove the VR compositor from the framework.

Remove the VR compositor framework and enable out-of-process VR composition
in VrCore.

This CL seems large due to the ripple effect of changing the VrFlinger
API and protocol types. There are three major modules that require
concurrent changes:
1. Protocol definitions and low-level VrFlinger API in libdisplay.
* Additional changes needed to keep old interfaces working for
a short time while replacing the dependent code (dvrGraphics*).
2. VrFlinger service implementation changes to support VrCore compositor
and the removal of the internal compositor.
3. Changes to libdvr platform library API due to changes in #1 and #2.

Because of the nature of the interdependence of types and other defs it is
difficult to break this CL into smaller chunks. However, review of the three
major modules (libdisplay, libdvr, and libvrflinger) may be done separately
to ease the mental burden on reviewers.

Change Summary:
- Remove obsolete screenshot service. VR screenshots will be implemented
by VrCore.
- Update display protocol definitions for changes in VrFlinger service
requirements. The majority of the changes in libdisplay are a
consequence of these protocol and service changes.
- Update VrFlinger to support two kinds of surfaces:
1. Application - use by VR apps.
2. Direct - used by VrCore (protected by permission check).
- Remove VrFlinger internal compositor and GL context.
- Remove obsolete debug console.
- Update VrFlinger hardware composer interface to handle direct
surfaces only, removing the concept of GPU (compositor) layers.
- Update display manager to expose access to application surface info
to VrCore (protected by permission check).
- Update libdvr platform library interfaces for changes to VrFlinger
API / protocol.
- Clean up libdvr API struct setup using a common include.
- Add C++ header-only helpers for DVR platform library opaque types.

Bug: 36401174
Test: Build; run VrFlinger display test tool.
Change-Id: I15abfde5f72dbb3725a3f58621486afba6b64902
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
0057fddc71d1c3c3de8f9d0bd45a51bb293bfa3c 02-May-2017 Jiwen 'Steve' Cai <jwcai@google.com> Deprecate producer/consumer usage: Step 2

Clean up bufferhub_rpc, display_rpc and service side producer/consumer
usage reference.

Next (final) step is to remove all remaining client side reference to
producer/consumer usage and update dvr_xxx API.

This also fixes a minor typo in dvr_named_buffer-test

Bug: 37881101
Test: Build, flash, ran particles.apk and buffer_hub_queue-test
Change-Id: Ibae4376c1fd1ed964843d8b2ad2fb27204fe5e28
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
2c38b56d19f464142e32030b99ac56afd47ab7cd 21-Apr-2017 Mathias Agopian <mathias@google.com> Plumb gralloc producer/consumer bits correctly

Bug: 33350696
Test: compile, boot device, cts
Change-Id: I2f078cf4bbdf0db49f2e914b051f55629fb37eb6
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
a5d404d8d4f6bb4efa95eaf6d857bc03224606fb 19-Apr-2017 Hendrik Wagenaar <hendrikw@google.com> DVRBuffer functions should acquire AHardwareBuffer

Bug: 37488135
Test: Updated DVR buffer tests
Change-Id: Ia255aca571e7162382e7be3c13be8ea192adbc90
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
db5763834df1b6a1a3aef9442982451f7505f402 18-Apr-2017 Hendrik Wagenaar <hendrikw@google.com> Dvr api usages should follow AHardwareBuffer

* Since vrcore doesn't have access to gralloc1 usages
* Since gralloc1 may be replaced in the future

Bug: 37435415
Test: TestNamedBufferUsage
Change-Id: Iaa47396aca26460541d1b9031dce0b971b630555
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp
eaa5522feac452703a0836310047d4b15702487d 06-Apr-2017 Hendrik Wagenaar <hendrikw@google.com> Convert the pose buffer into a more generic named buffer

* It's likely that we'll have more than one pose buffer
* It's cleaner to separate the vsync info into a separate buffer

Bug: 37001881
Bug: 37240552
Test: Added and manually ran TestNamedBuffersSetup
Change-Id: I76621d3cfa8c21c9d5d1e6e648854067673be9ab
/frameworks/native/libs/vr/libdvr/tests/dvr_named_buffer-test.cpp