Some additional context about why this is important (in relation to the blocking bug): eventually, we're going to want to set up a system where, before running Telemetry tests, we update the firmware of the attached BattOr to the firmware version that's currently in cloud storage. Right now, however, we have no way to ask a BattOr which version of the firmware it's using via the battor_agent. This bug tracks that feature.
Also updating to P1, as our current inability to update the firmware programmatically is resulting in failed Telemetry benchmarks on the chromium.perf waterfall.
Comment 1 by charliea@google.com
, Oct 3 2016Labels: -Pri-2 BattOr OS-All Pri-1
Status: Assigned (was: Untriaged)