On 06/08/2016 08:15 AM, Brian Starkey wrote:
Hi Laura,
On Mon, Jun 06, 2016 at 11:23:27AM -0700, Laura Abbott wrote:
The ABI for Ion's ioctl interface are a pain to work with. The heap IDs
are a 32-bit non-discoverable namespace that form part of the ABI. There's
no way to determine what ABI
On 06/06/2016 11:59 PM, Chen Feng wrote:
The idea is good, define the heap ids in header file is inconvenient.
But if we query the heaps information from user-space.
It need to maintain this ids and name userspace one by one. The code may
be complicated in different module user-space.
In
Hi Laura,
On Mon, Jun 06, 2016 at 11:23:27AM -0700, Laura Abbott wrote:
The ABI for Ion's ioctl interface are a pain to work with. The heap IDs
are a 32-bit non-discoverable namespace that form part of the ABI. There's
no way to determine what ABI version is in use which leads to problems
if
The idea is good, define the heap ids in header file is inconvenient.
But if we query the heaps information from user-space.
It need to maintain this ids and name userspace one by one. The code may
be complicated in different module user-space.
In android, the gralloc and other lib will all use
The ABI for Ion's ioctl interface are a pain to work with. The heap IDs
are a 32-bit non-discoverable namespace that form part of the ABI. There's
no way to determine what ABI version is in use which leads to problems
if the ABI changes or needs to be updated.
This series is a first approach to
