summaryrefslogtreecommitdiff
path: root/futility/futility.c
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2014-08-11 12:30:04 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-08-12 02:50:56 +0000
commit277dc5274c5c906c8d80d2ae4cc7679d234e8408 (patch)
tree15a31f5b8f4182795be133da654d97dec2c0cf98 /futility/futility.c
parent6014c048131f7c3d055e97c0aaa44494edc4f813 (diff)
downloadvboot-277dc5274c5c906c8d80d2ae4cc7679d234e8408.tar.gz
Add GBB flag to disable PD software syncstabilize-6146.Brelease-R38-6158.B
In order to disable PD software sync but still do EC software sync it is useful to have a separate GBB flag for it. This will allow me to release a Samus P2B firmware image that will update the EC but not the PD, since the PD FW that comes on P2B devices cannot be updated with software sync. BUG=chrome-os-partner:30079 BRANCH=None TEST=flash BIOS with updated EC+PD: 1) no GBB flags to override behavior updates both EC and PD 2) GBB flag to disable EC software sync disables both EC and PD update 3) GBB flag to disable PD software sync disables only PD update Change-Id: I49ffb59238bee4a2dd66b24f2516e3ce46ea06cd Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/211910 Reviewed-by: Bill Richardson <wfrichar@chromium.org> Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'futility/futility.c')
0 files changed, 0 insertions, 0 deletions