tree 3bd57b8415dd7d30923e87e57ba4ef666db15fea
parent b6089f03e107d5427fce44279634f229301462f3
author Simon Glass <sjg@chromium.org> 1375753324 -0600
committer ChromeBot <chrome-bot@google.com> 1376191594 -0700

cros_bundle_firmware: Ensure the flasher avoids silent/bootsecure

These options need to be disabled for the flasher. We don't want a silent
console since then it is impossible to see when the flasher finishes. We
don't want bootsecure since then the flasher script cannot run.

A previous interim change corrected the 'silent' flag - the change completes
the fix and will allow us to make an image self-flashing in a later change
(i.e. we pull out U-Boot and the FDT from the image to be flashed, and use
those to flash it).

BUG=chrome-os-partner:21115
TEST=FEATURES=test sudo -E  emerge cros-devutils
Flash U-Boot with 'crosfw -b peach_pit -SCF'

 -C means silent console
 -S means bootsecure

See that we still get messages from the flasher, and it succeeds in its task.

Change-Id: I7a96a041ffbab6dfae4adcf6827fa39e925c9fb7
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/64742