commit | 9b6adb0550c4f948bfd6dd9e738070a65c6c884e | [log] [tgz] |
---|---|---|
author | Manupa Karunaratne <manupa.karunaratne@arm.com> | Tue Sep 28 17:30:20 2021 +0100 |
committer | GitHub <noreply@github.com> | Tue Sep 28 09:30:20 2021 -0700 |
tree | 9636e83d973347d6b54958b09a240162406973b0 | |
parent | a6f9a25d68ffa8c7e3de958cf1c309ef7bc62f48 [diff] |
[RFC] Arm Ethos-U Integration (#11) * Arm Ethos-U Integration This commit adds markdown for Arm Ethos-U Integration into TVM along with the diagrams used within the RFC. Change-Id: I56b8918628f93aadfc08068a4adefaf880664ca7 * Arm Ethos-U Integration * fixing a typo in a link Change-Id: I9ab14c366f2c39ba36b8a43a83e4f15ea309712e * Arm Ethos-U Integration * adding the header for the RFC * modifying the paths to match the PR number Change-Id: Ice1c651c6619ae5d6a95fa70e739826b36a47af1 * Arm Ethos-U Integration *fixing the path to assets with the PR number *adding a white bounding box to compiler_arch to render in a black github interface for better viewing experience Change-Id: If52e34583cbd81614f0ba176a6fce8f440d8041c * Arm Ethos-U Integration * changed uNPU --> Ethos™-U Change-Id: I9b869396fef66772e70adc8cc90538434cc090ac * Arm Ethos-U Integration *addressed andrew's comments Change-Id: Id83f1d85d1105b524afd6fa33efa1051239edb03 * Arm Ethos-U Integration * further addressing comments Change-Id: I01c8f5721fc1aa650479b6d2fe4e0abde80b1de3 * Arm Ethos-U Integration *defined acronyms *fixed spelling convention *reffered to tracking issue for the upstreaming plan Change-Id: I623edc7171c21bfe65509d89422698ff7959086c
An RFC is a “Request for Change” to the TVM project. It is a design document that describes a new feature, enhancement, or process to the TVM project. RFCs should be the primary mechanism for proposing major features and changes. The author of the RFC is responsible for the discussion of the change, and for organizing the work around it. RFCs are text files, stored in the Apache TVM RFC repository, that serve as history and documentation of TVM features.
The primary audience of RFCs is the TVM development community. RFCs serve as a guide for the design and implementation of features during and after their development. A secondary audience is general users and developers who are interested in how and why a feature was designed and implemented.
To work on a major feature within the TVM project, an RFC must first be merged into the TVM RFC repository as a markdown file. Once merged, the RFC is considered to be “active” and may be implemented, with the goal of merging the implementation into the TVM project. These are steps that should be taken in the RFC process:
tvm-rfcs
repository. To allocate a new RFC number, open a PR against tvm-rfcs
(initially, you might need to use a dummy number in the filename for the RFC content; this can be updated after the RFC PR is created).L
to indicate it is a legacy RFC. For example, L0001
.Apache TVM is a compiler stack for deep learning systems. It is designed to close the gap between the productivity-focused deep learning frameworks, and the performance- and efficiency-focused hardware backends. TVM works with deep learning frameworks to provide end to end compilation to different backends.
© Contributors Licensed under an Apache-2.0 license.
TVM adopts Apache committer model. We aim to create an open source project that is maintained and owned by the community. Check out the Contributor Guide.