4 ms·
Problem is, while you can get most of the hardware documentation you'll need from the vendor you buy your chips from (despite them not technically being allowed
by StudentStuff 8y ago
Problem is, while you can get most of the hardware documentation you'll need from the vendor you buy your chips from (despite them not technically being allowed to redistribute it), you generally can't recompile radio baseband software for that 3G SOC you just bought, leaving you with something that can't be customized at its core. Want to optimize radio wakeups to increase battery life on your device? Good luck, you'll need to rewrite the baseband yourself!
- Barrin92 8y agoI think the benefits of open source in the hardware space aren't perfectly analogous to software. As you point out, due to the fixed and somewhat opaque nature of hardware, changing hardware yourself is far from trivial, what the Shenzhen ecosystem does allow for however is faster iteration within the market itself. More steps of trial and error within shorter time, more things are being recycled, more people get their hands on designs and so forth. This doesn't always directly make things more customizable, but it does increase the pace at which the ecosystem moves.
- StudentStuff 8y agoThe problem I see is that those iterations are constrained to not touch core parts of the hardware due to the lack of code and documentation being out there in public. Working with existing SOCs in different ways than their manufacturers ever thought possible is pretty common, many in the Linux-Sunxi community have pushed the envelope on how little power some SOCs can use, made possible in part by hardware features like a tiny, slow, power sipping RISC core that was on most Allwinner chips but was never leveraged before.