Call firmware wipe script during factory wipe if it exists

clobber-state

Index: clobber-state
diff --git a/clobber-state b/clobber-state
index e27caada3493933b3704997359938d4ece4904ba..2a28a4e3babe626a69c416d9200a4474b25727ad 100755
--- a/clobber-state
+++ b/clobber-state
@@ -112,6 +112,20 @@ echo 3 > /proc/sys/vm/drop_caches
 # Do any board specific wiping here.
 # board_factory_wipe.sh will be installed by the board overlay if necessary.
 if [ "$FACTORY_WIPE" = "factory" ]; then
+  FIRMWARE_WIPE='/usr/sbin/firmware-factory-wipe'
+  FIRMWARE_WIPE_LOGS='/mnt/stateful_partition/var/log/update_firmware.log'
+  if [ -x "$FIRMWARE_WIPE" ]; then
+    if [ "$DEVMODE" = "1" -o -f /root/.dev_mode ]; then

[Nick Sanders, 2011/03/05 04:46:43]

I don't think DEVMODE is set here.. 

+      # More message on console for developer mode and dev builds
+      FIRMWARE_WIPE_LOGS="/dev/tty1 $FIRMWARE_WIPE_LOGS"
+    fi
+    mkdir -p /mnt/stateful_partition/var/log
+    [ -z "$BOOT_SPLASH_PID" ] || wait $BOOT_SPLASH_PID

[Nick Sanders, 2011/03/05 04:46:43]

I don't think this will persist either?

+    chromeos-boot-alert update_firmware /dev/tty1
+    IS_CHROMEOS_STARTUP=1 "$FIRMWARE_WIPE" 2>&1 |
+      tee -a $FIRMWARE_WIPE_LOGS
+  fi
+
   BOARD_WIPE=/usr/sbin/board_factory_wipe.sh
   if [ -x "${BOARD_WIPE}" ]; then
     ${BOARD_WIPE}