tree c452608ac687103b7a5d03f403e51f94b74d4224
parent 3123fa1a7393aaa85b3b36171b4c1ccdf3d33fe3
author Nicolas Boichat <drinkcat@google.com> 1486464824 +0800
committer chrome-bot <chrome-bot@chromium.org> 1507001141 -0700

update_kernel.sh: Do not copy firmwares to DUT, by default.

By default, running, in ~/trunk/src/scripts:
./update_kernel.sh DUT_IP

will upload to the DUT:
 1. kernel
 2. modules (/lib/modules/vX.Y.Z)
 3. firmware (/lib/firmware)

1+2 are necessary to get the kernel booting, but uploading firmwares
can lead to unintended breakage, as the firmwares are usually built
using other ebuilds (e.g graphics drivers, linux-firmware, etc),
leading to all sort of possible mismatches (outdated developer build
environment, accidental updating to too-recent firmware on old kernel).

BUG=chromium:689448
TEST=./update_kernel.sh DUT_IP does not upload firmware
TEST=./update_kernel.sh --firmware DUT_IP does upload firmware

Change-Id: Iff7ad52f9da0bf04375d9e2d9cbee0b4c03415d7
Reviewed-on: https://chromium-review.googlesource.com/439046
Commit-Ready: Nicolas Boichat <drinkcat@chromium.org>
Tested-by: Nicolas Boichat <drinkcat@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>