From 80a90edd47d20141cfb7b18ededc9a3090fba58c Mon Sep 17 00:00:00 2001
From: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
Date: Fri, 4 Jan 2013 02:29:03 +0100
Subject: Work around MEMERASE ioctl for rk3066 compatibility

Due to a kernel bug and no available sources we have to work around the
MEMERASE ioctl - if used, it hangs and never returns. I straced the original
recovery executable and could see that it is simply calling write() with a
bunch of zeroes instead of using MEMERASE.

Added a hack that does the same and now the resulting TWRP recovery image works.

Change-Id: I1b1c1c9e870e350776346bdca5d442c7ef565aa0
---
 Android.mk | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'Android.mk')

diff --git a/Android.mk b/Android.mk
index 725436a0a..2f8c1942d 100644
--- a/Android.mk
+++ b/Android.mk
@@ -206,6 +206,10 @@ ifeq ($(TW_INCLUDE_JB_CRYPTO), true)
     LOCAL_C_INCLUDES += system/extras/ext4_utils external/openssl/include
 endif
 
+ifeq ($(TARGET_BOARD_PLATFORM),rk30xx)
+LOCAL_CFLAGS += -DRK3066
+endif
+
 include $(BUILD_EXECUTABLE)
 
 include $(CLEAR_VARS)
-- 
cgit v1.2.3