This caused the ION pointer to get clobbered with a UMP
pointer when FIMC1 memory was requested.
After a while, camera would be unable to allocate buffers
due to ION memory not being freed properly.
Change-Id: I1ba1d27da924a0bb81631548e83c7f3e5789f319
Building libsecril-client from source works perfectly well
on the i815. It will probably work well with the gsm devices
as well.
Change-Id: I4f394555d82fb48a86ea52212d9fb56ca0e8acd3
Two reverts squashed, due to Mali-derping being fixed
in frameworks/native:
Revert "gralloc: avoid using framebuffer"
This reverts commit 5125ccc5b6.
Revert "gralloc: Send first 2 FB buffers to carveout and next to UMP"
This reverts commit d288deb284.
Change-Id: I530dc255b7543e03d0e8277d3ad12ed11d6649ab
Mobile's blobs behave this way, except they don't do the
4k alignment done by the FIMC1 allocs.
The 4k alignment should fix issues such as NHK World Live TV,
but fails to do so.
Change-Id: I1ee4cd13e23f9f2f6c6616ee9eed1096b571a82c
Mobile's blobs don't appear to have been compiled with this
present in their headers, and none of the Insignal sources
actually use this.
Change-Id: Ib8611f6da90ea78aa8eec451c76f56ddb32b45a4
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>
Window 2 is used to query global info about the LCD.
Kanged from patch for aries by Greg Hackmann <ghackmann@google.com>
Change-Id: Idf754d4536337d6c06652c1d0c744dc7c0936b15
There are quite a few different Samsung devices which require
macloader (many of which are just using binary blobs), so we
should move it out of the device trees.
Change-Id: I9e23fca0ba4c17da328cace801a92fa57df9a862
Sampling rate change causes stutter while playing music.
Stutter appears randomly, but has a higher chance of appearing
when the screen goes from off to on.
Change-Id: I9b23212165203c7ff7ef65021be09fd366e55770
* Replace crespo-based VSYNC uevent mechanism in hwcomposer
with a custom IOCTL mechanism instead (required kernel
modifications.
* The VSYNC uevents were spamming the Android UEventObserver
and causing about 7% of constant CPU load
c86856efabfa0b2981ceb47898dc5873a4998707
Improve custom VSYNC handler in hwcomposer
* only poll when necessary
* solves suspend/resume instability?
45bf1dae7fa9057a3415151f7559e7bd2a162ead
Change-Id: Icdb5c60059e71688479d390b7b3a1f09a0315a5f
Patch Set 2: removed unused files,
as audio, camera and sensors are device specific
Patch Set 3: aries OMX
Patch Set 5: liblight patch for epic
Patch Set 9: liblight(s) is device specific, rmed it from here.
Change-Id: I57a3d5714037836bab441ee5a3e772c260fb21d4
blue and green leds are much stronger than the red one,
dim them down to get true colors (especially yellow).
Change-Id: I61c5f39e90e6392752a0e80a96e5e317427ea4a2
Our kernel sets the gyro to 500 DPS and not 2000 DPS.
In addition, X and Y are swapped and Y is not inverted.
Also change the orientation sensor conversion factors to
match that found in aries-common since the orientation
sensor seemed overly sensitive. However, the orientation
sensor might not actually do anything... Android may
be performing sensor fusion of other data to determine
orientation.
Change-Id: I03df5d7bac9d58881e360546af4cf77878802807
Andrew Dodd