summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Dodd <atd7@cornell.edu>2012-06-10 21:30:46 -0400
committerAndrew Dodd <atd7@cornell.edu>2012-06-10 21:30:46 -0400
commit02d3dd24907604e7f61f1baa15d3662c42b437fa (patch)
tree5a644519a9c8f72a953bb9d9ebeefd8f2fe5ce56
parent542bbcb2a161b8c9368cf81cdda48a437701bbe2 (diff)
downloaddevice_samsung_n7000-02d3dd24907604e7f61f1baa15d3662c42b437fa.zip
device_samsung_n7000-02d3dd24907604e7f61f1baa15d3662c42b437fa.tar.gz
device_samsung_n7000-02d3dd24907604e7f61f1baa15d3662c42b437fa.tar.bz2
n7000: Set BOARD_SUPPRESS_EMMC_WIPE
Nearly all N7000 units have a defective Samsung eMMC chip (VYL00M fwrev 0x19) that cannot handle MMC ERASE commands. This is the cause of rampant bricking of devices seen on XDA, especially since the shipment of official ICS releases like XXLPY. While our kernel currently blocks ERASE commands making this redundant, it's best to be doubly safe. Also, this should disable ERASE functionality in our updater-scripts, rendering them safe to flash even on "dangerous" kernels. (This needs testing to be sure.) Change-Id: Ice6e747faa7b715c3a2d8e28d962588d8436b174
-rwxr-xr-xBoardConfig.mk7
1 files changed, 7 insertions, 0 deletions
diff --git a/BoardConfig.mk b/BoardConfig.mk
index d9f6ff6..e5f98ee 100755
--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -140,6 +140,13 @@ BOARD_CHARGER_RES := device/samsung/galaxys2/res/charger
# assert, galaxynote needs to be removed later
TARGET_OTA_ASSERT_DEVICE := galaxynote,n7000,GT-N7000
+# Nearly all shipped N7000 devices have defective eMMC chips (VYL00M fwrev 0x19)
+# Prevent usage of ERASE commands in recovery on these boards.
+# This is redundant for our recovery since the kernel has MMC_CAP_ERASE
+# disabled for mshci.c, however it makes nightly ZIPs safer to flash
+# from kernels that still have MMC_CAP_ERASE enabled.
+BOARD_SUPPRESS_EMMC_WIPE := true
+
# Use the non-open-source parts, if they're present
-include vendor/samsung/n7000/BoardConfigVendor.mk