News for hackers. Stuff that matters.
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @05:18PM (#10873123)
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-l...

Love that they developed and open-sourced a 8Gbps, 1us, I/O interface. That might come in handy. :)

Re:Why I will be using RISC-V in my next chip by cmrx64 on Saturday January 09, 2016 @06:24PM (#10873292)
Agree! I love adapteva for a lot of reasons, and this makes me want to keep on piling the love.
[dead]
Re:Why I will be using RISC-V in my next chip by adapteva on Saturday January 09, 2016 @06:19PM (#10873278)
Nope, it's now MIT license!!
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @06:20PM (#10873283)
I didn't check licensing for GPL because I figure you knew better on HW. Glad you people chose wisely. :)
Re:Why I will be using RISC-V in my next chip by purpled_haze on Saturday January 09, 2016 @06:51PM (#10873405)
Even though it isn't GPL anymore, how exactly would it kill all hope?
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @07:09PM (#10873485)
How 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.

Re:Why I will be using RISC-V in my next chip by colejohnson66 on Saturday January 09, 2016 @09:06PM (#10873803)
How does the GPL prevent them from making money? Sure, I have essentially the source code of someone's processor, but unless I have millions of dollars to fabricate a chip, the source's only use is to learn how things work.

Intel, if they wanted to, could release the source code of their microcode for their processors under the GPLv2 and not provide the signing certificate (like TiVo did), and all people would be able to do with it is study it. What am I gonna do with the source code of a processor? Build an emulator? I already have the instruction manual...

Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @09:20PM (#10873851)
Main reply here:

https://news.ycombinator.com/item?id=10873839

Microcode is a separate issue that's debateable. Their CPU hardware, patents, logistics, ecosystem, and branding are real source of revenue. Microcode release might nit hurt them. However, it might contain trade secret methods for utilizing hardware in a clever way that could give competition (mainly startups) an edge. Biggest players, esp AMD, probably already RE'd it.

That said, Im for opening up microcode and even push for microcoded RISC-V. The reason is you can do all kinds of stuff from optimizing algorithms to atomic functions. There were also HLL-to-microcode compilers in the past to make it easier.

Look up PALcode on Alpha ISA if you want a nice hybrid, too.

Re:Why I will be using RISC-V in my next chip by userbinator on Saturday January 09, 2016 @10:30PM (#10874011)
That said, Im for opening up microcode and even push for microcoded RISC-V.

You mean a CISC-V? ;-)

Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @10:33PM (#10874023)
Lol. Clever. I'll keep it Microcoded RISC-V until people start doing something bloated like emulating x86 in it. ;)

cough Loongson people cough

Re:Why I will be using RISC-V in my next chip by wildmusings on Saturday January 09, 2016 @09:50PM (#10873920)
Intel has competitors. Why would Intel want to provide its competitors with what must be, at the very least, tens of millions of dollars worth of work?
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @10:27PM (#10874004)
You have the right idea but it's way more that you think. Intel spends over a billion dollars per quarter on all their tech.

https://ycharts.com/companies/INTC/r_and_d_expense

I agree R&D on any given bit of HW design is at least tens of millions. Probably more than once per year going back a decade given it's custom and formally verified. Standard cell approximating that would be a fraction of it but still ridiculously high if aiming for competitive performance/watt.

Re:Why I will be using RISC-V in my next chip by wildmusings on Sunday January 10, 2016 @12:04AM (#10874254)
Yeah, Intel is one of the biggest companies in the world. I was just speculating an absolute floor for just the microcode in particular.
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @12:43AM (#10874354)
You're the second person to bring up microcode. I'm curious why two are focused on this rather than the HW itself. What about you?

Note: For readers not in the know, microcode is the sequence of wiring activations of the physical, closed hardware. Instructions, merely series of bits, get translated to that by the microcode engine running from a memory rather than hardwired engine. Unlike the ISA, it's highly tied to the hardware since it drives it directly.

Re:Why I will be using RISC-V in my next chip by wildmusings on Sunday January 10, 2016 @02:00AM (#10874518)
I'm not focused on this, it was an example used in the post I responded to.
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @12:19PM (#10876065)
Oh OK
Re:Why I will be using RISC-V in my next chip by chei0aiV on Saturday January 09, 2016 @08:42PM (#10873739)
How does the GPL prevent those costs from being recovered?
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Saturday January 09, 2016 @09:15PM (#10873839)
By 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?

Re:Why I will be using RISC-V in my next chip by krupan on Saturday January 09, 2016 @11:39PM (#10874189)
"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?

Re:Why I will be using RISC-V in my next chip by adapteva on Sunday January 10, 2016 @01:56PM (#10876574)
There is no typical...but here are some guidelines

1.2x (companies are either ultra efficient, copycats, suicidal, or dumping)

2x (US companies shipping volume, healthy)

4x (goal for FPGA companies and mixed signal niche)

10x (goal for companies with monopolies)

100x (one-offs, like processors for military/satellite)

Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @02:34PM (#10876765)
I like that breakdown. That sounds about right. Especially the FPGA's and military. :)

Btw, I'd love a hardware engineeer's take on my idea for bootstrapping open hardware. The idea is HW development issues make it too costly. Led me to consider an open-source FPGA on 45nm or below with tool-chain. Let academics build (and open) the hardest stuff with non-profit integrating that with I/O and other key I.P. onto small number of chips selling it at cost.

Example open FGPA (a start, not end-goal) http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-43...

Example open-flow (add VPR or whatever FPGA tool is called) http://opencircuitdesign.com/qflow/

Idea is we get an easy FPGA set up to allow targeting with open or commercial tools. Its specs are open for review and enhancement. There is a via- or metal-configurable S-ASIC co-developed that matches its architecture. Like with eASIC, people can do an inexpensive conversion if they choose. Even considered using people they turned down in their contest (but whose stuff worked) to build the tooling for that. ;)

So, you have cheap-as-possible 45nm or below FPGA's being cranked out with more I.P. and tooling all the time. S-ASIC conversion is inexpensive due to matched architecture. If designed for it in mind, ASIC conversion wouldn't be too difficult either for FPGA-proven designs given staff and tooling. The HW cost is essentially some important cells, NOC, key IP (eg USB, PCI, DDR), memories, some analog, and at least one integration. With MPW's & academic support, it might cost a fraction of what it otherwise would. Not going to be EDA or HW competitive with Xilinx or Altera but not $600-$2,000 a chip w/ closed bitstream either.

My main worry outside market demand is effect of patent suits, esp if they demand royalties per unit. Otherwise, I'm hoping combo of academics, existing tooling, open FPGA's, and S-ASIC's is a solid combo for a start on widely-accessible, open HW. Still getting feedback from HW pro's before I start knocking on doors, though.

Re:Why I will be using RISC-V in my next chip by adapteva on Sunday January 10, 2016 @02:48PM (#10876833)
Before answering...what do you see as the problem today and what is your goal?
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @03:14PM (#10876962)
A few problems I'm trying to knock out in one solution. That's always risk but FPGA's are versatile. Here's a few:

1. Subversion and security concerns of all the black boxes in hardware alleviated with open I.P., tooling, and HW. Main concern in my field.

2. Both ASIC and FPGA entry cost to startups trying to get custom stuff out the door. Need to lower it.

3. Hobbyists and academics experimenting currently benefit from FPGA's with some HW and SW ecosystems built around them. I see that expanding with easy-to-use, open tooling. Plus maybe decent HLS system. Synflow is one I know in that niche.

4. I've been pushing potential of FPGA as accelerators for cloud, networked, and HPC applications for a while. There's an uptake in their use but cloud is cost-sensitive. FPGA's w/ OpenCL-style tooling sold at cost in boards pluggable into regular servers or desktops could... well, you know the potential because you're in that market & brave enough to compete on architecture. ;) Pico Computing also comes to mind with their FPGA desktops.

5. Maybe make HW prototyping, verification, etc cheaper as another source of revenue as I've seen some ASIC-oriented products that use FPGA's for this. I know many of the tools are too slow, too, so there's potential for straight acceleration as in 4.

6. Reduce cost (and runtime risk) of FPGA-proven components with S-ASIC conversion. Also thought about anti-fuse but think S-ASIC is legally & physically safer. Not a HW expert, though, so going on second-hand comments there.

So, there's at least 5 potential benefits from an open-source FPGA sold at cost. Especially on performance if people start cramming them into boards like Pico and Maxeler do with cloud company orders. Good on trustworthy, hobbyist, and prototyping ends with low cost & open, expanding SW side.

So, that's the idea. Pretty ambitious and with high failure potential for sure. It's why, if I attempt it, I'll be enlisting cloud companies and academics. AMD's "semi-custom" business seems to indicate some potential if it's integrated into a CPU's memory bus or a CPU itself. Core logic and stuff only needs to be done once on one good node. Subsequent integrations much cheaper.

Re:Why I will be using RISC-V in my next chip by adapteva on Sunday January 10, 2016 @03:45PM (#10877124)
You can get lattice FPGAs for a few dollars each from distributors. Zynq's in volume are reportedly as $15/each. Tools are free.

If cost is the main concern, then how low do you need to go?

An open FPGA arhitecture is a good thing, but it will require something akin to the RISC-V effort to make it happen. (ie major DARPA/NSF, academic, industry backing to bootstrap). Let's see what happens...

Re:Why I will be using RISC-V in my next chip by chei0aiV on Sunday January 10, 2016 @07:40PM (#10878036)
No, just a student doing a masters thesis can create an open FPGA:

https://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-4...

Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @08:30PM (#10878243)
I linked to that above. The conversation moved on because, as your paper noted, what they created lacks a lot of the functionality and even core elements of commercial FPGA's. I agree academics can do most or all of it but it will take more than one at Master's level to be competitive.
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @04:07PM (#10877212)
Subversion and amount of logic are main concerns. Lattice aint Virtex6 last I checked. I agree on RISC-V/DARPA comparison though.
Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @12:40AM (#10874341)
I'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.

Re:Why I will be using RISC-V in my next chip by analognoise on Sunday January 10, 2016 @02:43AM (#10874588)
100% sure - once you have the masks, pumping out chips is cheap, if you do it in volume.

http://www.adapteva.com/andreas-blog/semiconductor-economics...

Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @12:25PM (#10876093)
Key quotes:

"Super complex SOC platforms like Apple’s Ax family or the IBM Cell very likely exceeded $1B in total development costs and involved thousands of engineers in aggregate."

"Meanwhile relatively simple SOCs like the Epiphany family of chips were designed for less than $3M over the span of 3 years.[1,2]"

And Adapteva did such a good job being cheaper than average they wrote a [different] blog post about how they went about it. So, the low end was $3 million over 3 years while users wanting to ditch proprietary are asking for price/performance/watts closer to the above quote that cost $1 billion. Hence, my prediction it will take millions to tens of millions to make something acceptable. Also, me pushing Cavium's model of RISC multicore + HW accelerators for common things. I think it will help by taking load (& optimization) off the main CPU's.

Now, people doing analog stuff have it a lot easier given even 350nm is often good for that. That stuff can get really cheap:

http://www.planetanalog.com/author.asp?section_id=526&doc_id...

Re:Why I will be using RISC-V in my next chip by krupan on Saturday January 09, 2016 @11:29PM (#10874154)
How 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?
Re:Why I will be using RISC-V in my next chip by jeffbush on Sunday January 10, 2016 @11:32AM (#10875855)
I 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...

Re:Why I will be using RISC-V in my next chip by nickpsecurity on Sunday January 10, 2016 @12:30PM (#10876110)
I 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.

Re:Why I will be using RISC-V in my next chip by chei0aiV on Sunday January 10, 2016 @02:08AM (#10874531)
Copyright 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_desi...