Thanks for putting this out Andrew. Lots to unpack, but generally looks like a
good list.
On #6, I suspect a few of those stats could be gathered and reported prior to
shipping down to a device. (like mbed does for instance)
On #2, I wonder if perhaps something that runs daily against master
I think this is a really good idea. I was thinking of pitching the idea for BoF
but am glad you beat me to it.
As part of "next steps", I wonder if via the fora here we should assemble a
sort of mini list of protoRFCs in advance of the discussion.
---
[Visit
Topic](https://discuss.tvm.a
As more a policy kind of comment, for a fix release and the potential for more,
as a community, "we" might want to set some expectations for how long something
might be maintained / update frequency etc kind of akin to the linux kernel
community. (ex: https://www.kernel.org/category/releases.h
Sounds good. Looking forward to what you end up posting.
---
[Visit
Topic](https://discuss.tvm.ai/t/discuss-extending-utvm-micro-session-and-more-boards/6643/3)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https
Hi Everyone (especially fellow uTVM fans)
I've been looking at micro.device.arm.*, micro.Session and related code like
openocd_low_level_device.cc in src/runtime/micro.
At first blush I feel like we should be looking at other means to drive a
session besides perhaps OpenOCD especially when I
