It’s very neat that ThreadX and friends are MIT licensed now. I used ThreadX and NetX a bunch before the acquisition and open sourcing, and generally enjoyed using them. TX has a tight API / system design and implementation that makes it really nice to use.

I remember running into some obscure bugs with the NetX BSD socket layer that we ended up fixing in-house. It’s been way too long to dig up the specifics, but it’s great that fixes can now be upstreamed more easily.

> I remember running into some obscure bugs with the NetX BSD socket layer that we ended up fixing in-house. It’s been way too long to dig up the specifics, but it’s great that fixes can now be upstreamed more easily.

Unfortunately, it doesn't seem they have a process for that yet. But I'm sure that will improve. Or the community could take over. It would be nice to get a silicon vendor to pick this up to build a larger community around it.

> I remember running into some obscure bugs with the NetX BSD socket layer that we ended up fixing in-house. It’s been way too long to dig up the specifics, but it’s great that fixes can now be upstreamed more easily.

Yeah, I always had the impression their translation layers were afterthoughts. Never used the BSD one though.