44addfe5d29023045784293459fab78a5899863b |
|
14-Mar-2018 |
Jiwen 'Steve' Cai <jwcai@google.com> |
GraphicBuffer: add optional DetachedBufferHandle Stores a BufferHub handle that can be used to reattach this GraphicBuffer back into a BufferHub producer/consumer set. In terms of GraphicBuffer's relationship with BufferHub, there are three different modes: 1. Legacy mode: GraphicBuffer is not backed by BufferHub and mDetachedBufferHandle must be invalid. 2. Detached mode: GraphicBuffer is backed BufferHub, but not part of a producer/consumer set. In this mode, mDetachedBufferHandle must be valid. 3. Attached mode: GraphicBuffer is backed BufferHub and it's part of a producer/consumer set. In this mode, mDetachedBufferHandle must be invalid. Note that the DetachedBufferHandle is used as a opaque handle for GraphicBuffer and it's not exposed to VNDK. Bug: 38137191 Bug: 69982239 Bug: 70046255 Bug: 70912269 Test: GraphicBuffer_test Change-Id: I4c3a967cb498291aa175312fdadc84edd3b1a8be
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
dbbe33b95336efa74e8bb4ebcf6cba50919aa247 |
|
28-Sep-2017 |
Chia-I Wu <olv@google.com> |
libui: harden GraphicBufferMapper::importBuffer Add support for validateBufferSize and getTransportSize from IMapper 2.1. Update GraphicBufferMapper::importBuffer to validate buffer size, and update GraphicBuffer::flatten to use the handle transport size. This fixes two issues with GraphicBuffer. Pointers returned by lock/lockYCbCr can now be accessed without potential OOB. flatten no longer includes process-local runtime data. Bug: 62535446 Bug: 62084097 Bug: 32587089 Test: manual Change-Id: Ice13af26b84f25e43089637e9d67e3ad820e22ed
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
cb496acbe593326e8d5d563847067d02b2df40ec |
|
22-May-2017 |
Mathias Agopian <mathias@google.com> |
use 64-bits usage bits almost everywhere Revert "Revert "use 64-bits usage bits almost everywhere"" This reverts commit 1671de0068de40f57288628d4b757a1c84962a62. Test: manual, build Bug: 33350696 Bug: 38466700 Change-Id: Ia2f51b97137dba754b1938dfb1e235f4babc8a88
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
1671de0068de40f57288628d4b757a1c84962a62 |
|
22-May-2017 |
Guang Zhu <guangzhu@google.com> |
Revert "use 64-bits usage bits almost everywhere" Bug: 38466700 This reverts commit 175d98757d7d9003d4f64756cf4c2b366ba77e97. Change-Id: I5f08a4ca91511775cd52250d10a0220b258b8368
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
175d98757d7d9003d4f64756cf4c2b366ba77e97 |
|
16-May-2017 |
Mathias Agopian <mathias@google.com> |
use 64-bits usage bits almost everywhere Test: manual, build Bug: 33350696 Change-Id: Ida33c2a902155044651158467bb99d664e958c41
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
82c049843870fc72ff36f48b970dfaf413db0687 |
|
19-Apr-2017 |
Chris Forbes <chrisforbes@google.com> |
ui: Rework GraphicBuffer + Allocator for 64bit usage Removes gralloc1-style flags, and replaces with HIDL-style single 64bit usage. Internal storage of the usage is still 32bit; to be addressed with a future change. Change-Id: I60062208cbb06bc8cf6c293e7c7e1530c1147912 Bug: b/33350696 Test: Bullhead: booted to launcher, take photo, watch youtube
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
cb8405e7e74398aeafc9ef6ddb59af2d7cc6d2a6 |
|
18-Apr-2017 |
Chia-I Wu <olv@google.com> |
libui: remove gralloc0/gralloc1 support We now talk to HIDL gralloc exclusively. Bug: 37433368 Test: boots Change-Id: Iecd2f9a02c7066b2f33f24c1de57e9c4af8e28f5
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
5bac7f36ee9d5ed0c2e8a0141909ca94351965a8 |
|
06-Apr-2017 |
Chia-I Wu <olv@google.com> |
libui: update for revised HIDL gralloc The revised HIDL gralloc is implementable on top of gralloc0 and gralloc1, which enables us to remove all legacy code. However, it lacks the ability to query buffer properties from a buffer handle. GetBufferFromHandle in VR always fails. Bug: 36481301 Test: builds and boots on Pixel Change-Id: Id7cfa2d2172dfc008803860f24fcf4f03ba05f11
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
f543e5a7110868647e6dc16788b72ad7de80fa38 |
|
04-Apr-2017 |
Mathias Agopian <mathias@google.com> |
Remove useless GraphicBuffer() constructor Test: compiled & run Bug: 36869708 Change-Id: I83d80a1cde28671135b7716a434c503aeefcec46
/frameworks/native/libs/ui/GraphicBuffer.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/ui/GraphicBuffer.cpp
|
7992781a574b1c52a203e9271772da16f0f06812 |
|
23-Mar-2017 |
Jesse Hall <jessehall@google.com> |
Use gralloc usage conversion library Converting from ..graphics.allocator@2.0 usage to gralloc0 usage isn't quite as simple as ORing and truncating, which is what the default implementation was doing. Switch to using library functions that do it correctly. Test: boot bullhead Change-Id: Ibe644b53655e191b9bca9d619825a8918e8fc365
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
e9e9fe40fb702ab1390a32c61981bc927177258a |
|
01-Mar-2017 |
Mathias Agopian <mathias@google.com> |
fallout of cleaning-up libutils includes Test: run & compile Bug: n/a Change-Id: I99e462d2db6560742fa3f065d5de50cd60111130
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
311b479d7f50bc9e487cf9b4859843d0f4778382 |
|
01-Mar-2017 |
Mathias Agopian <mathias@google.com> |
clean-up EGL includes Test: compile and run Bug: cleanup Change-Id: Icb6c70c80d455446d7163a20d51c41d9b6e0b578
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
fe2f54fc8a9810708fe05d719721af19aea10a4a |
|
16-Feb-2017 |
Mathias Agopian <mathias@google.com> |
cleanup libui’s includes - remove unneeded includes - include a cpp’s header first in all cpps Test: compiled & booted Bug: 35164655 Change-Id: I0890913fcc6614cce156aff19fccdef183145beb
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
841abed655e96e51506ae6a78e6b4dab6740bfd7 |
|
11-Feb-2017 |
Mathias Agopian <mathias@google.com> |
clean-ups, remove warnings, fix includes. Test: built and run Bug: none Change-Id: I505df89e2263952d90fae432c5eaa7d00056c6f0
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
1c457103ccd9a520b723c1a90189d4e88a0bdd63 |
|
07-Feb-2017 |
Daniel Nicoara <dnicoara@google.com> |
VR: Update VR HWC and VR WM to use GrallocMapper Removes the gralloc hacks to access buffer internals and re-enables building of VR Window Manager. Bug: b/34878847 Test: Compiled Change-Id: I06aa5ec0428b2f282a36ee89dbc4da9838c25782
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
e96a325aff9da4e02abeb7b9178592583cf3b78c |
|
02-Feb-2017 |
Craig Donner <cdonner@google.com> |
Add methods for allocating and locking GraphicBuffers via gralloc1 flags Bug: 34050596 Test: manual Change-Id: I9515e60fe6b67d2c6f02b1bb78651669430f12ef
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
6ebc46a7c01b22bc19d3c00b493f8d930b15b43a |
|
22-Oct-2016 |
Craig Donner <cdonner@google.com> |
Add layered buffer support to libui and libgui. Bug: 31686534 Test: manual Change-Id: Ia40270701467f4b785660324cad883e7da08989a
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
9ba189dc5c03040d45dad2080a81115f48f099c3 |
|
22-Sep-2016 |
Chia-I Wu <olv@google.com> |
libui: add support for android.hardware.graphics Add Gralloc2::Allocator and Gralloc2::Mapper as wrappers to android.hardware.graphics.allocator@2.0 and android.hardware.graphics.mapper@2.0 respectively. Prefer Gralloc2::{Allocator,Mapper} in GraphicBufferAllocator/GraphicBufferMapper. The new path has these differences - it does not support gralloc0 - it does not dup-and-close fence fds to and from HAL (not sure why we did that) - release implies native_handle_close and native_handle_delete (same as in gralloc1?) When all interesting targets have android.hardware.graphics implementations, the old path will be removed. That is why the new path is added in the least intrusive way, as in: if (new-path-valid) { new-path; } else { old-path; } despite the ugliness. Test: booted to launcher, tested with YouTube and some games Change-Id: Idabb6c62e73c96a59736b497c6d6d1366095e7e3
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
024e9313ce69ced1f853d737de680ef9f50ed26d |
|
24-Aug-2016 |
Dan Stoza <stoza@google.com> |
Add requestor name to GraphicBuffer alloc metadata Adds a requestor name (usually the BufferQueue consumer's name) to the metadata that GraphicBufferAllocator stores on allocation so that `dumpsys SurfaceFlinger` can attempt to attribute buffer usage to the correct client. Bug: 30776557 Change-Id: I6e0f346584c871bb3b9d5481f82b697b0475a916
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
8deb4da6e8fe4687991da32ae68fa0bca4cb8212 |
|
02-Jun-2016 |
Dan Stoza <stoza@google.com> |
libui: Convert Allocator and Mapper to gralloc1 Converts GraphicBufferAllocator and GraphicBufferMapper to speak gralloc 1.0 (via the C++ shim and optionally the 1On0 adapter) instead of gralloc 0.x. Bug: 28401203 Change-Id: Ie1649f0ee72801579be2c2d3c47177b52962a825
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
22e4cc36cd965046ea1b17376a40bdf3b6e23301 |
|
16-Sep-2015 |
Praveen Chavan <pchavan@codeaurora.org> |
libgui: assign handle to NULL after free to avoid use-after-free situations. Change-Id: If9c09f509bc55795856302e5ca34470df019c622
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
53390e1e8c33ebee5bb8100e846f5263ba05ff73 |
|
04-Aug-2015 |
Pablo Ceballos <pceballos@google.com> |
libgui/SF: Fix some code warnings A couple of fixes to satisfy the Eclipse static code analysis tool. - Initialize all members in constructors - Remove unused forward declarations - Add parentheses when combining logical and bitwise operators - Fix a case statement with no break (it was intentional) Change-Id: Icecb8cc98c6f58b97ab33fffb621f0edc33a7d3c
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
812ed0644f8f8f71ca403f4e5793f0dbc1fcf9b2 |
|
03-Jun-2015 |
Dan Stoza <stoza@google.com> |
libgui: Add generation numbers to BufferQueue This change allows producers to set a generation number on a BufferQueue. This number will be embedded in any new GraphicBuffers created in that BufferQueue, and attempts to attach buffers which have a different generation number will fail. It also plumbs the setGenerationNumber method through Surface, with the additional effect that any buffers attached to the Surface after setting a new generation number will automatically be updated with the new number (as opposed to failing, as would happen on through IGBP). Bug: 20923096 Change-Id: I32bf726b035f99c3e5834beaf76afb9f01adcbc2
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
958f501189a29e53767f41bc8172e4af8d1ce2bf |
|
24-Apr-2015 |
Dan Stoza <stoza@google.com> |
Merge "libgui: Allow an IGBProducer to disable allocation"
|
9de7293b0a1b01ebe6fb1ab4a498f144adc8029f |
|
17-Apr-2015 |
Dan Stoza <stoza@google.com> |
libgui: Allow an IGBProducer to disable allocation Adds a new method IGBP::allowAllocation, which controls whether dequeueBuffer is permitted to allocate a new buffer. If allocation is disallowed, dequeueBuffer will block or return an error as it normally would (as controlled by *ControlledByApp). If there are free buffers, but they are not of the correct dimensions, format, or usage, they may be freed if a more suitable buffer is not found first. Bug: 19801715 Change-Id: I0d604958b78b2fd775c2547690301423f9a52165
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
eea6d682b8b0f7081f0fe8fab8feadb16e22b30b |
|
20-Apr-2015 |
Dan Stoza <stoza@google.com> |
libui/libgui: Fix errors in parceling BufferItem and GraphicBuffer were not parceling correctly, which had not been noticed because the libgui tests (specifically, one that tests placing a BufferQueue in a separate process from the IGBP/C) had not been run recently. This change fixes the errors found in those classes. Change-Id: Ie224361a534a79115a3481d83ff97f21d154d4f5
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
c168b8a5a9dcc0e45e32fc3cd40b9410e0288fb1 |
|
18-Feb-2015 |
Michael Lentine <mlentine@google.com> |
Update maxNumber to be smaller. There shouldn't be more than 4096 fds (probably signficantly smaller) and there shouldn't be more than 4096 ints. Cherry pick of I3a3e50ee3078a4710e9737114e65afc923ed0573 Bug: 18076253 Change-Id: I82a883572b401f115d252dcd3d00aa7252b49b0e
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
133caacf87423a738f31b6e1f58d0abcb377058d |
|
02-Dec-2014 |
Dan Stoza <stoza@google.com> |
Fix -Werror on 64-bit builds Add another static_cast to avoid an error on 64-bit builds Change-Id: I62fb2c67766c4aab70d9d1834f255d06ff82dd8d (cherry picked from commit 116c7a113cb2db4d3f7708627ac4713c7e92cd43)
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
d31824004277f554000417cea349d69f18655e95 |
|
17-Nov-2014 |
Dan Stoza <stoza@google.com> |
libui: Enable -Weverything and -Werror Enables -Weverything and -Werror, with just a few exceptions for warnings we can't (or shouldn't need to) work around. Change-Id: I470a267e9b1c373f2d5c960f005c3b0e02b2db63 (cherry picked from commit 303b9a51239d36d237a7d40c67b5085cdb3c1059)
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
01049c8321aab30cd431e2febeddd79242ae5a4f |
|
11-Nov-2014 |
Dan Stoza <stoza@google.com> |
Enable clang for libui/libgui/surfaceflinger Enables clang and C++11 for libui/libgui/surfaceflinger, and eliminates all compile-time warnings. Change-Id: Ie237fdb5ae44f2bfcddaa884f9c65ec3f08ae50f (cherry picked from commit f10c46ef855b6410b20ebd8b1351d4d78d8eca8e)
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
38803268570f90e97452cd9a30ac831661829091 |
|
31-Oct-2014 |
Michael Lentine <mlentine@google.com> |
Fix for corruption when numFds or numInts is too large. Bug: 18076253 Change-Id: I4c5935440013fc755e1d123049290383f4659fb6 (cherry picked from commit dfd06b89a4b77fc75eb85a3c1c700da3621c0118)
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
18fae75350bcd5f19ef90afb533e3fbedfd4c83b |
|
23-Jul-2014 |
Colin Cross <ccross@android.com> |
crash if getNativeBuffer() called on NULL GraphicBuffer If getNativeBuffer() is called on a NULL GraphicBuffer the static_cast of this from GraphicBuffer* to ANativeWindowBuffer* will return a small pointer like (ANativeWindowBuffer*)0x10. This value can propagate past NULL checks until it causes a crash far away from the original NULL pointer. Crash immediately instead. Change-Id: Id614b9eb1484108b3c3c733545309844c4b87532
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
f974bffb36a97d21432a504a741330c4f4245746 |
|
12-May-2014 |
Greg Hackmann <ghackmann@google.com> |
am 38c9e132: am c1ffd351: am bd20e551: Merge "Use asynchronous lock/unlock API" * commit '38c9e1327a5b24267c3dab5293bc9d7ada6e9fc9': Use asynchronous lock/unlock API
|
8f3960179c56767e5077be8337792bd4e244b7d7 |
|
01-Apr-2014 |
Francis Hart <fhart@nvidia.com> |
Use asynchronous lock/unlock API The gralloc API now provides a way for using lock/unlock with the Android explicit synchronisation concept. This changes updates the GraphicBuffer class to also expose this functionality, and updates the Surface class to make use of in line with the dequeueBuffer/queueBuffer mechanism. This new behaviour is dependent on GRALLOC_MODULE_API_VERSION_0_3. If the local gralloc module does not support this then the existing synchronous lock/unlock mechanism will be used. Change-Id: I8c3fd9592e0c5400ac9be84450f55a77cc0bbdc5
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
2f3dca149a2bcae96f18e38f7ba99a95c3e1b08c |
|
10-May-2014 |
Greg Hackmann <ghackmann@google.com> |
am 9493d492: am 9eb142e3: am a9d49f99: Merge "Revert "Use asynchronous lock/unlock API"" * commit '9493d4924a59f14b698389386337a9c07a7ea3c4': Revert "Use asynchronous lock/unlock API"
|
02528cf6aaedbbfec55be57d33389e1c57d88245 |
|
09-May-2014 |
Greg Hackmann <ghackmann@google.com> |
am 4b46776f: am 8a6cd189: am f60564a1: Merge "Use asynchronous lock/unlock API" * commit '4b46776ff88c5a365700b88e8b2b04e1b2c77e6e': Use asynchronous lock/unlock API
|
a9d49f99e69d8fc0e60b492b131322c96f47a232 |
|
09-May-2014 |
Greg Hackmann <ghackmann@google.com> |
Merge "Revert "Use asynchronous lock/unlock API""
|
53ec72523a4083b88eaa13e2e720976523a7ebf8 |
|
09-May-2014 |
Greg Hackmann <ghackmann@google.com> |
Revert "Use asynchronous lock/unlock API" This reverts commit 378ef07760eda717367d9429428c42d54d54d9a7. Change-Id: I1de5ab973b5383633e75924fe90ac3ca8216c36a
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
f60564a13e917877c76c99294194a621d872076b |
|
09-May-2014 |
Greg Hackmann <ghackmann@google.com> |
Merge "Use asynchronous lock/unlock API"
|
378ef07760eda717367d9429428c42d54d54d9a7 |
|
01-Apr-2014 |
Francis Hart <fhart@nvidia.com> |
Use asynchronous lock/unlock API The gralloc API now provides a way for using lock/unlock with the Android explicit synchronisation concept. This changes updates the GraphicBuffer class to also expose this functionality, and updates the Surface class to make use of in line with the dequeueBuffer/queueBuffer mechanism. This new behaviour is dependent on GRALLOC_MODULE_API_VERSION_0_3. If the local gralloc module does not support this then the existing synchronous lock/unlock mechanism will be used. Change-Id: I77daa1beb197b63b1c2f281b8414ac4ae4b5b03c
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
e2d1157381b863a94ccb36a1c6d70cad47e79c1a |
|
29-Apr-2014 |
Jun Jiang <jun.a.jiang@intel.com> |
fix GraphicBuffer::flatten crash issue when handle is null Change-Id: I0d3727e4366cac355791e52cb7790bf8f3c51527 Signed-off-by: Jun Jiang <jun.a.jiang@intel.com>
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
b1363d37fc6a661508fad106eb7698c5850a6c17 |
|
28-Mar-2014 |
Dan Stoza <stoza@google.com> |
Add unique ID to GraphicBuffer Adds a globally-unique ID (PID + sequence number) to every GraphicBuffer, which will remain the same while crossing Binder, even if the underlying handles change. Change-Id: Ib11330a4c5e99621b82204e0adb31b9a88658426
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
bc96e4714f4cc1ae598f122b3b9f7998c09fe674 |
|
18-Mar-2014 |
Andy McFadden <fadden@android.com> |
Added null check Don't dereference "handle" if it's NULL. Bug 13348578 Change-Id: Ifa6758616c41cf84467af6db29c779d26901a01c
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
771ed8d71be8c851991164cd10fcfbf2431df86d |
|
13-Aug-2013 |
Jesse Hall <jessehall@google.com> |
am fc43e16a: Merge "Graphics:Add error check when create GraphicBuffer" * commit 'fc43e16a5693bca0edfc82c650fb606971e47138': Graphics:Add error check when create GraphicBuffer
|
2aff7025482cc40d2ebd45f81cdb318ac1c6f868 |
|
20-Nov-2012 |
Lingyun Zhu <lingyun.zhu@intel.com> |
Graphics:Add error check when create GraphicBuffer Change-Id: Ib0ca59bf1dfe4ae0266c29c91c1dbe3d02c0904e Author: Lingyun Zhu <lingyun.zhu@intel.com> Signed-off-by: Lingyun Zhu <lingyun.zhu@intel.com> Signed-off-by: Shuo Gao <shuo.gao@intel.com> Signed-off-by: Bruce Beare <bruce.j.beare@intel.com> Signed-off-by: Jack Ren <jack.ren@intel.com> Author-tracking-BZ: 50141
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
87f9b877964b7d7db9b59ba45b73b4b1a779ecf8 |
|
01-Aug-2013 |
Mathias Agopian <mathias@google.com> |
remove unused code form GraphicBuffer Change-Id: I0dd67f1f93f654331e8f17b55730931dbc695ca7
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
e142428a9c8b9d2380032cd4d7b55ee440fe8770 |
|
30-Jul-2013 |
Mathias Agopian <mathias@google.com> |
Make Flattenable not virtual Fallout from the Flattenable change, update all its uses. Additionnaly, fix/tighten size checks when (un)flatten()ing things. Removed the assumption by some flattenables (e.g.: Fence) that the size passed to them would be exact (it can and will be larger in some cases) The code in Parcel is a bit complicated so that we don't have to expose the full implementation (and also to keep the code smallish). Change-Id: I0bf1c8aca2a3128491b4f45510bc46667e566dde
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
c43946b931de5dafd28f49963f9af78e05390b26 |
|
05-May-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Add support for HAL_PIXEL_FORMAT_YCbCr_420_888 - Add fields to CpuConsumer::LockedBuffer for new information - New lock methods for GraphicBuffer and GraphicBufferMapper for the format Bug: 8734880 Change-Id: If31f82c62d64b6942cf4cc6e5715585c03273f12
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
d69097f936d9780957a51ce77335ae409b32aaa3 |
|
30-Aug-2012 |
Jamie Gennis <jgennis@google.com> |
libgui: add some error checks This change adds a few error checks both in the framework and in some tests. Change-Id: I2baf2676942a0dc15866e75852a775a0091ed16d
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
5f2165f9455d4893b581b73a67c5431f4344b47e |
|
25-Feb-2012 |
Mathias Agopian <mathias@google.com> |
remove dependency on android_native{s_priv|buffer}.h Change-Id: Ie4b95f7061c240f37c504414259f92d72c4ffc89
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
e6f43ddce78d6846af12550ff9193c5c6fe5844b |
|
06-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGE(_IF) to (IF_)ALOGE(_IF) DO NOT MERGE See https://android-git.corp.google.com/g/#/c/157220 Bug: 5449033 Change-Id: Ic9c19d30693bd56755f55906127cd6bd7126096c
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
697526bc9e44ce61c88614f98387ae8bbf0a187e |
|
01-May-2011 |
Iliyan Malchev <malchev@google.com> |
frameworks/base: android_native_buffer_t -> ANativeWindowBuffer Change-Id: Idc2eabaa805bb6d308ebb315872623f28d428417 Signed-off-by: Iliyan Malchev <malchev@google.com>
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
b5a00fcb71426492f248ed49a0514a9b8d385065 |
|
08-Dec-2010 |
Mathias Agopian <mathias@google.com> |
am 48f42f8c: am 4153bf3a: Merge "[3171580] don\'t automatically log GraphicBuffer allocation failures" into gingerbread * commit '48f42f8c3fbd33b2f46c6290ff5963dd58938cf9': [3171580] don't automatically log GraphicBuffer allocation failures
|
678bdd6349344df254cc0c3377a40fd99e216635 |
|
04-Dec-2010 |
Mathias Agopian <mathias@google.com> |
[3171580] don't automatically log GraphicBuffer allocation failures some of these failures are not fatal and even expected in some cases so they should not emit a dump in the log in those cases. Change-Id: Idcfa252e3bfa9d74e27fe4ad8f8623aa01aa9c5e
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
309d3bb2f902163356f9d40b6d45c11b435d77a9 |
|
07-Oct-2010 |
Jamie Gennis <jgennis@google.com> |
Move binder magic from the Surface class to GraphicBuffer. - Register buffers with Gralloc when unflattening a GraphicBuffer (rather than doing it in the Surface class). - Add support for a GraphicBuffer that wraps an android_native_window_t*. Change-Id: I029ac086111bbac800e5ca37eb505f558b718cd8
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
a8f3e4e53cad835d0d57b85a6ce1b7416e95ba73 |
|
01-Jul-2010 |
Mathias Agopian <mathias@google.com> |
fix live wallpapers on Droid On omap3 h/w we force opaque formats to RGB_565 instead of RGBX_8888 because the GL driver doesn't support it. RGBX_8888 is always remapped to RGBA_8888. Change-Id: I0bfabeb98c8d3a399079e6797cf2a0ee95915324
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
579b3f88d03d06b897b778bd11818f5104677d1d |
|
09-Jun-2010 |
Mathias Agopian <mathias@google.com> |
allow re-targetting of surfaces Surfaces can now be parcelized and sent to remote processes. When a surface crosses a process boundary, it looses its connection with the current process and gets attached to the new one. Change-Id: I39c7b055bcd3ea1162ef2718d3d4b866bf7c81c0
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
b7e930db175c192464cebdeb49eb56cf6dd60114 |
|
02-Jun-2010 |
Mathias Agopian <mathias@google.com> |
split surface management from surface's buffers management Change-Id: If3c5655d1231f8f0c49ba68f972b1b20c93b3f87
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
49753266d2219d2fbf5c33dc4626f299dffcdd76 |
|
13-Apr-2010 |
Mathias Agopian <mathias@google.com> |
fix a bug where fading in/out of opaque 32-bits windows wasn't working opaque 32-bits windows are now allocated as RGBX_8888 buffers and SurfaceFlinger always uses GL_MODULATE instead of trying to optimize to GL_REPLACE when possible (makes no sense on h/w accelerated GL). we still have a small hack for devices that don't support RGBX_8888 in their gralloc implementation where we revert to RGBA_8888.
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
98e71ddaede9a0bfb681fd237bec1f66c6c53193 |
|
12-Feb-2010 |
Mathias Agopian <mathias@google.com> |
remove a dependency of GraphicBuffer (libui) on Parcel (libbinder). Add a Flattenable interface to libutils which can be used to flatten an object into bytestream + filedescriptor stream. Parcel is modified to handle Flattenable. And GraphicBuffer implements Flattenable. Except for the overlay classes libui is now independent of libbinder.
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
6fee064809068fe1a7da63d55678d9a222b0be15 |
|
03-Nov-2009 |
Mathias Agopian <mathias@google.com> |
fix[2228133] pixelflinger ignores the "vertical stride" leading to artifacts when playing back video we lost the concept of vertical stride when moving video playback to EGLImage. Here we bring it back in a somewhat hacky-way that will work only for the softgl/mdp backend.
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
54ba51dff21de666c5ae3bf3abd4f0634ebb0676 |
|
27-Oct-2009 |
Mathias Agopian <mathias@google.com> |
fix [2143798] Need to figure out how to do video Use EGLImageKHR instead of copybit directly. We now have the basis to use streaming YUV textures (well, in fact we already are). When/if we use the GPU instead of the MDP we'll need to make sure it supports the appropriate YUV format. Also make sure we compile if EGL_ANDROID_image_native_buffer is not supported
/frameworks/native/libs/ui/GraphicBuffer.cpp
|
3330b203039dea366d4981db1408a460134b2d2c |
|
06-Oct-2009 |
Mathias Agopian <mathias@google.com> |
fix [2167050] glTexImage2D code path buggy in SurfaceFlinger When EGLImage extension is not available, SurfaceFlinger will fallback to using glTexImage2D and glTexSubImage2D instead, which requires 50% more memory and an extra copy. However this code path has never been exercised and had some bugs which this patch fix. Mainly the scale factor wasn't computed right when falling back on glDrawElements. We also fallback to this mode of operation if a buffer doesn't have the adequate usage bits for EGLImage usage. This changes only code that is currently not executed. Some refactoring was needed to keep the change clean. This doesn't change anything functionaly.
/frameworks/native/libs/ui/GraphicBuffer.cpp
|