Over at the https://discuss.tvm.ai/t/rfc-ethosn-arm-ethos-n-integration/6680/16 thread, there was an interesting point made by @tqchen. I wanted to expand on the matter, while not hijacking the other thread.
https://discuss.tvm.ai/t/rfc-ethosn-arm-ethos-n-integration/6680/17 The reason I find this interesting is as follows: * BYOC has been a successful interface between TVM and vendors * VTA is the historical template of accelerator programming with full TVM stack * Yet the VTA codebase does not, currently, have a BYOC adaptation It seems to me, that the most assumed usage of BYOC has been as accepting Relay as an input language to the dedicated codegens (see ARM and Hexagon). But as tqchen pointed out, there is nothing against doing the codegen hand-off at the TIR level. This will in turn allow an eventual usage of AutoTVM as part of the BYOC compilation flow. I was wondering how a BYOC adaptation of the VTA example would look like? I think this would be a good way to generate better visibility of the TE/TIR level infrastructure of TVM and also important for adoption. --- [Visit Topic](https://discuss.tvm.ai/t/byoc-and-the-vta-missing-link/6867/1) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/f2b6b07f5e9d26bfca51455e870027b2c1d89ea31e3513b8824db149474b1f0b).
