8 ms·
Good that they're getting on the bandwagon as they're already popular with maker types. I also like the serendipity where this post led me to an equally excitin
by nickpsecurity 11y ago
Good that they're getting on the bandwagon as they're already popular with maker types. I also like the serendipity where this post led me to an equally exciting one:
http://www.adapteva.com/announcements/an-open-source-8gbps-low-latency-chip-to-chip-interface/ http://www.adapteva.com/announcements/an-open-source-8gbps-l...
Love that they developed and open-sourced a 8Gbps, 1us, I/O interface. That might come in handy. :)
- stolsvik 11y agoGPL License - kills all hope.
- adapteva 11y agoNope, it's now MIT license!!
- nickpsecurity 11y agoI didn't check licensing for GPL because I figure you knew better on HW. Glad you people chose wisely. :)
- purpled_haze 11y agoEven though it isn't GPL anymore, how exactly would it kill all hope?
- nickpsecurity 11y agoHow much do you see going on in GPL'd hardware despite tools and motivation being available going back decades? Almost nothing. Takes expensive tools, limited expertise, expensive masks for prototyping... all sorts of expenses that mean it virtually doesn't happen unless cost can be recovered. Stuff is so outrageously expensive and difficult at better nodes that re-using proven (costly) I.P. is the norm. Hence, you're going to need something that integrates with proprietary if you want them to build on it. There's still the possibility of a LGPL-style thing where at least re-synthesized or optimized versions of the open-source part must be re-released. However, forcing that for I.P. it integrates with would kill adoption by any provider unless they like operating at six to eight digit losses. Annually.
- chei0aiV 11y agoHow does the GPL prevent those costs from being recovered?
- nickpsecurity 11y agoBy allowing anyone to knock off the chip without paying back the R&D. There's already a huge market of counterfeits and clones coming out of China for most things you can think of. It's even easier without reverse engineering: hand design to a fab, individual or MPW, then package and sell the chips. Very little of the price of chips you buy is the material or packaging costs. It's mostly R&D recoup, marketing, administrative, and profit. Most of these companies get all that straight through sales of the chips. Eliminate everything but a tiny margin over physical costs and whats left for further development?
- krupan 11y ago"Very little of the price of chips you buy is the material or packaging costs." Are you sure about that? How much markup over material costs is there on most chips?
- nickpsecurity 11y agoI'm not sure on most chips. I do know if you look up MOSIS, etc prices you'll find that most of the cost of the prototyping run is the masks. The masks start at tens of thousands then just go up from there. High-end nodes are in millions to tens of millions. Every prototype run of your chip takes a new mask. Hence, all the money spent on proprietary tooling to reduce odds of digital or physical defects. Many ASIC's still need respins. Then, there's 3rd party stuff like I/O packages. Now, compared to that, the silicon wafer might cost a few grand with packaging (not volume) costing $10-20 a unit. For any OSS project, dare I say most of the cost will be in the first paragraph and recouping it will take significant unit prices. How significant depends on what's being sold and at what volume. A PIC or AVR clone at modest volume will be cheaper than an Oracle T2 clone at low volume. Hope that helps.
- 11y ago
- krupan 11y agoHow does the GPL apply to hardware? Let's say I take some GPL'ed verilog code, modify it a bit, build a chip out of it and sell the chip. Am I required to provide the verilog "source" for my chip? I guess if the chip counts as "object code" in GPL lingo then the answer is yes. There's a lot more than just the verilog code that goes into building a chip though. How is the physical layout, for example, handled? Is that considered part of the "corresponding source" in GPL lingo?
- chei0aiV 11y agoCopyright doesn't apply to physical hardware but it probably applies to hardware designs. There are various laws protecting ICs but I'm not sure they allow for copyleft-like hacks. https://en.wikipedia.org/wiki/Integrated_circuit_layout_design_protection https://en.wikipedia.org/wiki/Integrated_circuit_layout_desi...
- jeffbush 11y agoI found an interesting and detailed legal analysis of that. It sounds like the answer isn't black and white: http://jolt.law.harvard.edu/articles/pdf/v25/25HarvJLTech131.pdf http://jolt.law.harvard.edu/articles/pdf/v25/25HarvJLTech131...
- nickpsecurity 11y agoI was hoping someone jumped in for context. The other two commenters provide that. Now, in that context, let's just say that the ASIC ecosystem with companies sitting on hundreds of millions to billions in I.P. aren't about to (a) integrate a GPL component or (b) let their stuff be used in a GPL component if there's even the slightest chance it causes legal risk. That's all the good ones. The only exception I know (and promote) was Aeroflex Gaisler putting an ASIC-proven CPU and peripheral IP in a GPL release. That people did nothing with. (sighs) Even he's not doing GPL for new stuff IIRC. The rest continue licensing on a per-producer basis... revenue which GPL would negate. So, it's just incentives. The positive incentive is licensing, which they're doing. The negative incentives are anything risking their I.P., which GPL does. It's a double whammy against GPL'd or even free HW from existing ecosystem.
- cmrx64 11y agoAgree! I love adapteva for a lot of reasons, and this makes me want to keep on piling the love.