You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the various packages of rtic-scope require *nix IOTCTL commands for communicating with the TTY and there's some unix socket streams used as a mechanism to move data between the various sources and sinks.
It would be desirable to remove all uses of os-primitives to develop rtic-scope to be platform-independent. Given that probe-rs and other core utilities run on Windows and other supported OSes, it seems like thsi shouldn't be too difficult to refactor
The text was updated successfully, but these errors were encountered:
The largest hurdle (if one at all; I have yet to dive back into it) is refactoring the direct ioctl calls out. Its purpose is to mimic the configuration that screen /path/to/dev <baud rate> applies, specifically for FT232 variants.
Currently, the various packages of rtic-scope require *nix IOTCTL commands for communicating with the TTY and there's some unix socket streams used as a mechanism to move data between the various sources and sinks.
It would be desirable to remove all uses of os-primitives to develop rtic-scope to be platform-independent. Given that probe-rs and other core utilities run on Windows and other supported OSes, it seems like thsi shouldn't be too difficult to refactor
The text was updated successfully, but these errors were encountered: