HNHacker News
TopNewBestAskShowJobs

evevuecrl

2 karma · joined December 19, 2022

submissionscomments
evevuecrl··on RFC2217 implementation written in Rust
> The "serial port" setting, not the "tcp port" setting.

Oh that makes more sense, thanks!

> Serial ports don't negotiate a speed, so you have to be able to configure the right speed on both ends of the communication

This is actually why I was asking -- I'm messing around with an espflash-like clone and wanted this feature; so is the idea that its easier to set up the negotiation because of the command structure of telnet (e.g. pattern match on rx `telnet send ayt`)?

evevuecrl··on RFC2217 implementation written in Rust
> I assume you mean passes raw data received from TCP/IP through?

Yeah `impl TcpStream`

> lets you change the port settings

Might just be lack of familiarity with telnet, but wouldn't this be fairly easy to do `impl TcpStream`? In other words, why not just add this into espflash?

evevuecrl··on RFC2217 implementation written in Rust
What is the advantage to using this RFC instead of just having a server that writes to (or reads from) a serial port?
evevuecrl··on RFC2217 implementation written in Rust
Had never heard of this RFC and think it might be useful. Is there an example to try with the C3?