Google Git
Sign in
chromium/chromiumos/platform/tflite/refs/heads/firmware-cr50-prepvt-16155.B
commit
f435e870be4046a280c0a52ba34d7dd7fb50539b
[log]
author
Shik Chen <shik@chromium.org>
Fri Dec 27 07:08:53 2024
committer
Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>
Mon Jan 06 13:40:27 2025
tree
3a55dfc3b9dda54a297a9db0a95f26324f4c016d
parent
ca135a0c0a58331c6a607bd57b7a4707d93f0fa8 [diff]
tflite: Add README for patch management

BUG=b:359512663
TEST=Previwe markdown in Gitiles

Change-Id: Ib8940327d4c261908ddc6cf67bf1ae02cf3a4ce7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/tflite/+/6124639
Reviewed-by: Tommy Chiang <ototot@google.com>
Tested-by: Shik Chen <shik@chromium.org>
Auto-Submit: Shik Chen <shik@chromium.org>
Commit-Queue: Shik Chen <shik@chromium.org>
2 files changed
tree: 3a55dfc3b9dda54a297a9db0a95f26324f4c016d
  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.