Google Git
Sign in
chromium/chromiumos/platform/tflite/refs/heads/firmware-R145-16552.2.B
commit
af44f187898d93c12e6e666d8b0f4fdaa15234b4
[log]
author
Tommy Chiang <ototot@google.com>
Sun Dec 21 19:54:15 2025
committer
Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>
Mon Dec 22 02:55:34 2025
tree
9d9c4fa7ab184e7f31fa2b9b785b6e6a1c76fb73
parent
3d6cb8332b343a60a3272f33091657ae76a0ed55 [diff]
Remove completed TODO

The patch management logic is moved here in crrev.com/c/5334638

BUG=b:314854484
TEST=none

Change-Id: Iacb14a573b2774a4b0bad3fb66dbe6a6d4e898da
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/tflite/+/7274900
Reviewed-by: Shik Chen <shik@chromium.org>
Commit-Queue: Tommy Chiang <ototot@google.com>
Auto-Submit: Tommy Chiang <ototot@google.com>
Tested-by: Tommy Chiang <ototot@google.com>
1 file changed
tree: 9d9c4fa7ab184e7f31fa2b9b785b6e6a1c76fb73
  1. android/
  2. common/
  3. delegate/
  4. patch/
  5. script/
  6. tool/
  7. udev/
  8. .bazelignore
  9. .bazelrc
  10. .bazelversion
  11. .clang-format
  12. .gitignore
  13. BUILD.bazel
  14. CPPLINT.cfg
  15. DIR_METADATA
  16. OWNERS
  17. PRESUBMIT.cfg
  18. README.md
  19. WORKSPACE.bazel
README.md

ChromeOS TFLite

This repository hosts the core ChromeOS TFLite components, enabling on-device machine learning (ODML) workloads accelerated by NPU.

The corresponding ebuild can be found at: tensorflow-9999.ebuild

TensorFlow Patch Management

Patches are stored in the patch/ directory and explicitly listed in WORKSPACE.bazel. A helper script, ./script/patcher.py, is included to facilitate patch management within a TFLite workspace.

The typical workflow:

  1. Eject (Download) TensorFlow Source Code

    Download the TensorFlow source code into a local git repository with patches applied as individual commits:

    ./script/patcher.py eject

    This creates a new local git repository at tensorflow/.

  2. Modify the TensorFlow Repository

    Make changes to the tensorflow/ repository as needed, following standard git workflows. Optionally, include a PATCH_NAME= tag in commit messages to specify the filename of the corresponding patch.

  3. Seal the Repository

    Regenerate the patch files and update the WORKSPACE.bazel file:

    ./script/patcher.py seal

    This updates the patches in the patch/ directory and reflects the changes in WORKSPACE.bazel.

It's preferred to submit changes to upstream TensorFlow first and cherry-pick them as patches. This helps minimize divergence and makes TensorFlow updates easier.