4 ms·
vxWorks, eCos, WebOS, Symbian, RISCOS, the BSDs, and QNX aren't exactly special to a board. Nor are L4 or Mach single-platform kernels. If it's a bit cheaper p
by cestith 8y ago
vxWorks, eCos, WebOS, Symbian, RISCOS, the BSDs, and QNX aren't exactly special to a board. Nor are L4 or Mach single-platform kernels.
If it's a bit cheaper per unit to port something that's not Linux onto something you never expect an end user to access directly, that's what a manufacturer is often going to do. There are toolchains for many operating systems for many processors. Not all the world is Linux and not all the world is designed to be a general purpose computer system.
The reason these low price developer/maker boards are designed is because they can be put together for a low price. They reuse components designed to run a stack or maybe one of a few stacks in embedded devices produced at scale. Either the board maker supports it, or if enough demand for the software exists the community will help support it.
- pedrocr 8y agoI know all those exist and are possible. My point is that if you have a full stack of software already developed for pretty much all your range (like TP-Link does) bringing up a whole new one with Wifi drivers, NAT stack, etc just for the low-power device seems like way too much effort. I went and checked and couldn't find any TP-link device that wasn't Linux based, and they do sell very low end stuff.