This is the story of poor }. It is a painful saga.
Samsung left } floating inside the galaxy of framebuffer_alloc,
unable to join its brethren on the planet of STANDARD_LINUX_SCREEN
when they were shifted out of the #ifdef dimension.
codeworkx brutally eliminated poor } from the galaxy, it was
nowhere to be seen. codeworkx then took pity on the } and
placed it back on the planet of STANDARD_LINUX_SCREEN, but
placed it on a continent where it was all alone, unable to
ever see its mate {
Take pity on poor }, let it rejoin its people on the correct
continent of the planet STANDARD_LINUX_SCREEN, so they may
all shift out of the #ifdef dimension together.
Change-Id: I7a700b73ccd2c91f91d9af3704930759f46978c7
Taken from QCOM gralloc:
commit d80a52cbf961d737f6f3beef47b868a581b98591
Author: Saurabh Shah <saurshah@codeaurora.org>
Date: Tue Oct 2 14:32:40 2012 -0700
gralloc: Send first 2 FB buffers to carveout and next to IOMMU
Gralloc uses the GRALLOC_USAGE_HW_FB flag to allocate memory from carveout.
This is fine for primary framebuffer, but for external framebuffer we need IOMMU
heap buffers, since the ioctls for external work with those.
Ideally, the primary buffers also need to come from IOMMU heap, which is ongoing
work. This patch allocates the first 2 FB buffer requests (assuming they are for
primary) from carveout and allocates all subsequent buffers from IOMMU heap.
Bug: 7124159
Change-Id: Ie53b2e1e7fcac136acd2d251f39cefe367fc7125
Signed-off-by: Iliyan Malchev <malchev@google.com>
Andrew Dodd