Catching up with all the messages here, it looks like there are two problems and two solutions for the subsets of `tvmc` commands in discussion:
**P1:** **How can we create something that allows uTVM to be integrated bare-metal and RTOS?** This is aimed to provide TVM/TVMC as *tools* to be integrated as part of an embedded process. The target user knows about their project (how to build it in the most optimised way, how to flash it on a board, how to debug, etc.) and will fit something we provide in the Model Library Format as part of their workflows. * **S1:** This is solved by using the improving `tvmc compile` to generate a more comprehensive set of outputs in the Model Library Format, so that users can pick what is relevant for them (header files, static object files, boilerplate glue, etc). `tvmc run` has no role in this "uTVM" use case. **P2: How to test/tune operators and models using TVM/TVMC, when aiming at embedded devices?** This relates to TVM developers, that not necessarily know a lot about embedded development, but want to validate and check performance using embedded targets. * **S2:** In this case, we would have the proposed `tvmc micro` namespace, which would be basically aimed for testing and to bridge TVM with already existing tools, provided by each RTOS flavour the community decides to integrate with. This also would need to enhance `tvmc tune`, so that we could support uTVM tuning on this workflow. With all that, I just wanted to check we are talking about the same end-users when we say _users_, and to seeing the problems we are solving them with new commands, and who are the commands aimed at. Do you see any other fundamental problems we are trying to solve with all being discussed in this thread, that is not captured here? --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-tvmc-add-support-for-tvm/9049/13) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/43eeae7bee2c055a1faf0dff16848342cd3f88edea412a6d9d65941776c37586).
