areusch commented on pull request #8940: URL: https://github.com/apache/tvm/pull/8940#issuecomment-914619644
i chatted a bit more with @mehrdadh about the question of how to represent the (target, arduino_board) or (target, zephyr_board) pairs. It sort of seems like the neatest solution is to place the mapping in `microtvm_api_server.py` and make `server_info_query` return a suggested `target` based on the ProjectOption provided by the user to e.g. `tvmc`. My hesitations in doing this are: 1. right now Project API is entirely "downstream" of TVM--it just consumes a specified artifact of TVM and doesn't configure TVM. doing this would change that relationship. this means if TVM e.g. evolves the defintion of target to split it into pieces, Project API implementations may need to be updated. I'm not sure this is a big deal, but it's something to think on. 2. Since we would likely move the `tvm.target.micro` shorthands into Project API servers, it means that all platforms are suggested to make a Project API implementation even if they don't use the project generator. This wouldn't be required, though--you could still specify the target the old-fashioend way. it just could be a burden in some cases. we could always alleviate it by allowing platforms to create something specific to them. right now this is essentially test configuration. I think we could continue to import microtvm_api_server from these tests until we resolve this question. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
