History log of /hardware/libhardware/modules/gralloc/mapper.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
65d51a15a772e010ac60fc1a6481ba80a82d4513 05-Dec-2014 Elliott Hughes <enh@google.com> Remove ARCH_X86.

Should have been __GLIBC__, but the code is dead anyway.

Change-Id: I773f296a9c31949fa631cad863b841584c71f0ef
/hardware/libhardware/modules/gralloc/mapper.cpp
febaaa937f2bb08197ab5636afce210028357888 06-Feb-2014 Colin Cross <ccross@android.com> gralloc: fix warnings

Fix LP64 pointer casting warnings, unused parameters, and
turn off missing initializer warnings.

Change-Id: Idb70f4534282fed64ae81cb1e154d3f5b93091b0
/hardware/libhardware/modules/gralloc/mapper.cpp
0287721d284c8f067f25b3dce4b594e2154708ce 26-Nov-2013 Rom Lemarchand <romlem@google.com> gralloc: delete unused mutex declaration

Change-Id: Ibc7e70887b61f7dd885c86d412387636d3a6a867
/hardware/libhardware/modules/gralloc/mapper.cpp
0d8f81a9848b47afd7f4a75cda9955a5cc77b465 29-Mar-2013 Jesse Hall <jessehall@google.com> Log when creating a second buffer mapping in a process

Bug: 8468756
Change-Id: Ia883f459ea9e2648ca4a0b5a6f09ded4f46f13b3
/hardware/libhardware/modules/gralloc/mapper.cpp
c71b6caece3fb1b85327f05acdd1becae4eda137 28-Mar-2013 Jesse Hall <jessehall@google.com> Remove pid check in register/unregister

The register/unregister gralloc calls were avoiding
mmapping/munmapping the shared memory region if the buffer was created
by the current process. This is left over from the pmem-based
implementation, where trying to map the same region twice in the same
process would fail, or would reuse a single mapping without
refcounting.

This causes problems if a buffer is
- allocated in process A,
- transferred from A to process B and registered there
- unregistered/freed in A
- transferred back from B to A and re-registered

Process A then has a new handle to the buffer, but since it originally
created the buffer it will not be mmapped, so trying to read or write
the buffer will crash.

With ashmem, mmaping a region twice in the same process creates two
distinct mappings which can be used and munmapped independently. So
we no longer need to avoid mmapping again in the allocating process.

Bug: 8468756
Change-Id: I167bec5ca07e5534c5e2115630fe8386e481388e
/hardware/libhardware/modules/gralloc/mapper.cpp
60d056bf2926357260592409dee31374fa8e301b 08-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: I0cbe865d464a37365fa3be84948b07e5a0d181d0
/hardware/libhardware/modules/gralloc/mapper.cpp
cee8501c1623765d5287fcd440fbf8001b9de183 20-Dec-2011 Steve Block <steveblock@google.com> Rename (IF_)LOGD(_IF) to (IF_)ALOGD(_IF) DO NOT MERGE

See https://android-git.corp.google.com/g/156016

Bug: 5449033
Change-Id: I98e83cc9d22f0ea8fbf397ccccd9ce7773119551
/hardware/libhardware/modules/gralloc/mapper.cpp
f96b2064d7753af7ab75f05eff9559f401e1a4ad 15-Dec-2009 Mathias Agopian <mathias@google.com> remove all references to pmem and simplify the lock/unlock hooks

this gralloc module is only used on the emulator or without a h/w
renderer. therefore there is no synchronization to do in lock/unlock
and pmem buffers are not relevant.

hopefully this will remove some of the confusion about how gralloc
should be implemented and make it more obvious that this implementation
is not intended to be used by h/w renderers.
/hardware/libhardware/modules/gralloc/mapper.cpp
05eacf533eb90f79f4af43e9cf86cdb3817a00ca 14-Jul-2009 Mathias Agopian <mathias@google.com> better logs
/hardware/libhardware/modules/gralloc/mapper.cpp
bd80b38f2945ac918f66fb336c149b28b9dd030e 08-Jul-2009 Mathias Agopian <mathias@google.com> more fixes for [1965730]. We now free (unmap) both ashmem and pmem regions.
/hardware/libhardware/modules/gralloc/mapper.cpp
a4b587cb063dfd1b11f0006b0149e5e3045cc873 07-Jul-2009 Marco Nelissen <marcone@google.com> Simulator build fixes for the new GL stuff. The simulator still doesn't run, but at least it builds.
/hardware/libhardware/modules/gralloc/mapper.cpp
8c4ab1fa14cc13c324bde91c0271f9ab5f4663d3 12-Jun-2009 Mathias Agopian <mathias@google.com> pmem allocator in gralloc. enabled for all surfaces. currently it uses a lot more address space than needed.
/hardware/libhardware/modules/gralloc/mapper.cpp
5115665397e5f5be5a5d464bc22b70b023d243d9 10-Jun-2009 Mathias Agopian <mathias@google.com> with the new lock/unlock API we don't really mean reference counting on mmap/munmap because we're guaranteed to map the buffers only once within a process.

no need to track all handles anymore, which simplifies the code a lot.
/hardware/libhardware/modules/gralloc/mapper.cpp
82f7c041552e52b7e6eb44d9f7e99959599c2da4 04-Jun-2009 Mathias Agopian <mathias@google.com> suppress spurious debug log
/hardware/libhardware/modules/gralloc/mapper.cpp
485e69809aef8bf301b6bf19c03dc2d7693aaa1a 06-May-2009 Mathias Agopian <mathias@google.com> better documentation and implementation for lock/unlock
/hardware/libhardware/modules/gralloc/mapper.cpp
988b8bd553180e8d71b4028ecb721f46312efe62 04-May-2009 Mathias Agopian <mathias@google.com> lock will now return the vaddr of the buffer. map/umap are gone.

- make sure to return an error if a buffer is locked twice or unlocked while not locked.
- added registerBuffer() and unregisterBuffer() to the gralloc module so that we can do some cleanup when a buffer is no longer needed. this became necessary after we removed map/unmap so we have a place to unmap buffers without the need of a kernel module.
- change the constants for GRALLOC_USAGE_SW_{READ|WRITE}_NEVER to 0, so that NOT specifying them means "NEVER".
/hardware/libhardware/modules/gralloc/mapper.cpp
a8a75166a2d3c7639a7432a67075c98796165206 10-Apr-2009 Mathias Agopian <mathias@google.com> Integrate from //sandbox/mathias/donut/...@145728

SurfaceFlinger rework for new EGL driver model support.
/hardware/libhardware/modules/gralloc/mapper.cpp