Google Git
Sign in
chromium / chromiumos / infra / proto / 25fe2a700565c2cd07da71f4fa8460b9f5eab4c8
commit25fe2a700565c2cd07da71f4fa8460b9f5eab4c8[log] [tgz]
authorJon Murphy <jpmurphy@google.com>Fri Nov 07 00:36:26 2025
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Nov 07 01:59:09 2025
treef9f1b18b59e03c907d6c8ef1536dd9ad322649ad
parent9fa8b4e3bf5ffb247d67422a4eeeb8b8a5291b77 [diff]
firmware_builder: Add ec-legacy_renode target

BUG=b:456553702
TEST=./generate.sh

Change-Id: I1df0b7427e70a4bebd0fdcd967b6ae03888f582f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/7129094
Auto-Submit: Jon Murphy <jpmurphy@google.com>
Reviewed-by: Cindy Lin <xcl@google.com>
Commit-Queue: Cindy Lin <xcl@google.com>
3 files changed
tree: f9f1b18b59e03c907d6c8ef1536dd9ad322649ad
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.

When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.