Closed #98.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/98#event-14259027789
You are receiving this because you are subscribed to this thread.
Message ID:
@gromero PTAL, thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/98#issuecomment-1450804427
You are receiving this because you are subscribed to this thread.
Message ID:
This RFC proposes a structure to bring on-device testing on non-cloud supported
hardware targets in TVM.
Co-authored-by: David Riazati [driaz...@octoml.ai](mailto:driaz...@octoml.ai)
cc @areusch @leandron
You can view, comment on, or merge this pull request online at:
https://github.com/apac
This RFC proposes adding multiple module support in Model Library Format.
cc @gromero @areusch
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm-rfcs/pull/76
-- Commit Summary --
* MLF with Multiple Module RFC
-- File Changes --
A rfcs/0075
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/68#issuecomment-1124005594
You are receiving this because you are subscribed to this thread.
Message ID:
@gromero thanks for initiating this conversation. I think this is an important
topic to consider as the TVM contributions are growing. Having a guideline that
the community has accepted is important so the reviewers could use as a
reference to make decisions. But more importantly, I totally ag
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/10471#issuecomment-1058537881
You are receiving this because you are subscribed to this thread.
Message ID:
This sounds great! Thanks @driazati!!
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-allow-merging-via-pr-comments/12220/3)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/ema
@areusch issues that I have mentioned here are solved. Can we close this issue?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/8595#issuecomment-989965293
+1
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/9504#issuecomment-969899983
I have tested v0.8 release on microtvm physical hardware for Arduino and Zephyr
platforms. It passes the tests for these hardware:
- **Zephyr**: qemu_x86, nrf5340dk_nrf5340_cpuapp, nucleo_l4r5zi,
stm32f746g_disco, nucleo_f746zg
- **Arduino**: due
--
You are receiving this because you are subscr
Thanks for the changes. LGTM!
---
[Visit
Topic](https://discuss.tvm.apache.org/t/pre-rfc-tvmc-add-support-for-microtvm-targets/11221/21)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.or
+1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/9057#issuecomment-924238947
+1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/8928#issuecomment-913468833
Follow up issues that should be fixed:
- The latest fix on this PR breaks on NRF board which seems to be because of
`prj.conf` misconfiguration.
- stm32l4r5zi_nucleo is removed from the hardware target list.
- It also fails on disco board with similar error to NRF:
```
may be incomplete.
make[2]:
15 matches
Mail list logo