4 ms·
Maybe that's why they're cheap.
by StavrosK 8y ago
Maybe that's why they're cheap.
- TeMPOraL 8y agoI may completely misunderstand how the design process works here, but I'd assume the cheapest SOCs would be the most popular ones, and hence most likely to have proper support. Why isn't it so?
- walrus01 8y agothe cheapest ones are sold for embedded purposes where a manufacturer of a single specific device is using a vendor-supplied kernel, or not linux at all (vxworks or something). Look at the OS that runs on a $25 TP-Link home 802.11n/ac router for example. The manufacturer of the chip doesn't particularly care about making it work with a debian stretch environment, or similar.
- chx 8y agoI have a ELECOM WRH-583 router, dual band, dual Ethernet and at 65 * 35 * 20.5mm I am rather forgiving about not having Linux support. Two dimensions of the three are dictated by the two RJ45 sockets, 2 * 15.24 wide and 15mm high. The router itself has less than 44 * 30 mm PCB area to spend on actual router circuitry. SoC & 5G - PHY: RTL 8881AM, 2.4G - PHY: RTL 8188ER, RAM: ESMT M14D 5121632 (64MiB), NOR: MXIC 25L64 (8MiB). https://pbs.twimg.com/media/Crq6x3PUEAA58NW.jpg https://pbs.twimg.com/media/Crq6x3PUEAA58NW.jpg info from http://twisave.com/ysks/2016/9/p:5 http://twisave.com/ysks/2016/9/p:5 and these sort of routers are apparently not Linux compatible / capable even?
- ryukafalz 8y agoAnd this is why just about every embedded Linux device more than a few years old runs an ancient kernel with known vulnerabilities.
- imtringued 8y agoWell if you're running them headless then running armbian with a recent kernel will work on a lot of boards. The big problems come when you want driver support e.g. proprietary GPU drivers for ARM GPUs don't work because they were written for an old kernel api and ARM would rather focus on selling new GPUs than supporting older ones for sake of the tiny SBC niche.
- jnurmine 8y agoSome of those embedded devices are not even designed to be updated on the field. And some have support planned for a limited time and then anything resembling support is dropped. No company is going to support a product forever without getting money for it. So either the support is priced in or it is not, and if it is not, the product is correspondingly cheaper but then you get what you get. And people tend to select cheap, so there are no or few updates. Bottom line: embedded Linux devices with outdated software and security holes are that way through conscious intent, really. Running aftermarket firmware sometimes helps (the consumer), but only if there are no crazy things like binary blobs involved, since porting those is unlikely to be feasible.
- walrus01 8y agoIn my opinion this is a big argument in favor of the security benefits and update ability, if you're a company putting thousands of remotely managed devices out into the field, for using an x86-64 architecture. Yes it might be more costly and expensive to have NUC sized things, but you can also be confident that you can run a fully patched OS on it in 12 or 15 years from now. If I had a core 2 duo based 1U appliance from 2007 somewhere I could quite reliably update it to Debian 9.6 or the latest centos.
- pedrocr 8y ago> Look at the OS that runs on a $25 TP-Link home 802.11n/ac router for example. Aren't these usually Linux too for simplicity? There is still an extreme low end doing special embedded OS just to avoid a bit of extra RAM? Seems like a poor tradeoff from just reusing almost everything else from your existing range.
- cestith 8y agovxWorks, 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.
- dannypgh 8y agoJudging from a quick search, it looks like this SoC was developed for DVB-S receivers. I'm guessing nobody had "run Linux" as a requirement for their satellite receiver, hence the reason this work to be supported by Linux didn't have to happen before production and sale of this chip at large scale.