Re:USB-C Explorer – A development board to get started worki...
by whitequark_ on Sunday September 02, 2018 @04:29AM
(#17896175)
> But it's not like you can build a solid TCP stack these days either simply by reading the original late 70s RFCs.
I literally did this. It's called smoltcp (https://github.com/m-labs/smoltcp) and we use it in production as an lwIP replacement with great results.
Re:USB-C Explorer – A development board to get started worki...
by adiusmus on Sunday September 02, 2018 @05:39AM
(#17896357)
‘You can’t.”
‘You can and I have running code”.
This is why HN is great.
Re:USB-C Explorer – A development board to get started worki...
by andrewflnr on Sunday September 02, 2018 @10:47AM
(#17897162)
Does it work reliably on the open internet? AIUI, it's interoperability with all the edge cases of badly implemented protocols that leads to statements like GPs.
Re:USB-C Explorer – A development board to get started worki...
by kachnuv_ocasek on Sunday September 02, 2018 @04:32AM
(#17896187)
I love Hacker News. I was just looking for this library to use in my embedded toy.
Re:USB-C Explorer – A development board to get started worki...
by etaioinshrdlu on Sunday September 02, 2018 @05:45AM
(#17896368)
I think it would be cool if a project had a self-imposed token count limit. The project would never be allowed to grow more than X tokens long.
Then you can guarantee the project is small and haiku-like forever!
LWIP started off small, and it grew...
Re:USB-C Explorer – A development board to get started worki...
by whitequark_ on Sunday September 02, 2018 @07:50PM
(#17899307)
The "smol" in "smoltcp" is mostly talking about the internal architecture and exposed API. For example, it will never support true zero-copy sockets, because the API burden due to restricting itself to safe Rust is too high.
I don't think any TCP/IP implementation is going to be "haiku-like", the protocol stack is way too messy.
It sucks that the standard is so complex that a small number of design houses and consulting shops will end up with a de facto cartel of understanding the Sacred Knowledge, but nobody's stopping you coming up to speed by reading the whole spec and doing a lot of implementing. But it's not like you can build a solid TCP stack these days either simply by reading the original late 70s RFCs.
And you don't have to use this spec -- you can still use RS-449 if you think the USB spec has become overly complex. In fact I used that in a design only a few years ago!