system_api: Add `force_fw_update` field

.. to UpdateCheckParams to allow clients/callers into update_engine to
force a FW update.

BUG=b:228121045
TEST=emerge

Change-Id: I4fe391fac328841046c7a88c106a56c03b8d408c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/4119740
Reviewed-by: Henry Barnor <hbarnor@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Jae Hoon Kim <kimjae@chromium.org>
Commit-Queue: Jae Hoon Kim <kimjae@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: cfa626a0843f32389c6a0134277289aeab5b7aab
1 file changed
tree: dcb7c4a23ec1b34f5fc11e1e7577b00a51380741
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. DIR_METADATA
  11. LICENSE
  12. OWNERS
  13. README.md
  14. system_api.pc
README.md

This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files. No implementation should be added.

When writting a .proto file make sure to use:

option optimize_for = LITE_RUNTIME;

This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you mean. "Required is Forever" and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.