6 ms·
Open cores, ISAs, etc.: what is open about them?
- turbinerneiter 5y agoI think that the patent threat will crumble with more and more complex features being implemented on the Open Source cores, like BOOM and so on. I don't think that ideas that are taught commonly at university and are all over GitHub will be able to stay "owned". The question than will be how close we can come to the proprietary systems and which use-cases are low-key enough that their cutting edge new innovations don't make a difference. I think the microcontroller space will be wholly owned by RISC-V in the long run. For cheap, commoditized stuff, open is better than closed for everyone. For the high performance stuff, the manufacturer still needs to protect their investment, especially because the will need to invest more and more for ever smaller gains. Do you think that makes sense or am I phantasizing? :D
- netr0ute 5y agoI think for the high-performance stuff, history will repeat itself like with China's silk production. The "silkworms" (today's silicon IP) will eventually become open and everyone will know how China did it.
- mananaysiempre 5y agoChina’s silk industry attempted to prevent replication by withholding information: in today’s lingo, that’s not patents, that’s trade secrets. Those are intentionally mutually exclusive: the motivation for patents was quite literally to prevent knowledge being kept secret and eventually lost by granting time-limited exclusivity in exchange for public disclosure. (That’s why you can’t get a patent for something that was previously published elsewhere, even if it was you publishing it.) In theory, every patented technique is already public: it’s described by the text of the patent. In practice, today’s patents are malicious compliance writ large: most of the time, they describe only the most indispensable (not necessarily the most difficult) parts of the processes in the most obtuse language possible. And while I hold that a patent lawyer’s job is morally repugnant, the overall fault is hardly with those exploiting loopholes, it’s with those who cast the loopholes in stone (making them part of national law, pervasive international agreement bundles such as the WTO, etc.) in the first place.
- MisterTea 5y agoSomeone eventually has to build the hardware and that's the really expensive part. Arm has the upper hand here as they deliver more than just an ISA, they can sell you a whole silicon and software stack including engineering expertise to help get your thing to market. Plus they control the ecosystem so you're not going to run into odd edge cases (e.g. Loongson which is sorta MIPS). Not saying that companies like SiFive are not competent but they are just one player in what will become a very big game.
- turbinerneiter 5y agoDo you think that fabs like TMSC or global foundries will develop tools to support IP designers with this, to drive their own business? There is stuff like that going on in PCB design, where manufacturers make free design software, or distributors making footprint libraries.
- MisterTea 5y ago> There is stuff like that going on in PCB design, where manufacturers make free design software, or distributors making footprint libraries. Totally different things. Asking TMSC how to design a RISC-V chip is akin to asking Advanced Circuits or OSH Park how to design an Intel motherboard. They can make the board for you, but they dont design it.
- turbinerneiter 5y agoIt's not about asking them how to design a chip, it's about them providing the tools needed to go from a Verliog design to something they can manufacture.
- gimmeThaBeet 5y agoSo I would say to that extent they do, the foundries provide dev kits with cells to use on their process, and there's definitely the same incentive, good reusable IP gets you products faster which gets them more business. I think a lot of the landscape is just driven by the sheer cost of getting it wrong. Spinning a pcb is a bummer. Needing a new mask set is so much worse. There is eFabless, among other efforts in the vein you describe, they do a multi project wafer shuttle thing that google sponsors using skywater. It's supposedly an open source PDK, I haven't used it. https://github.com/google/skywater-pdk https://github.com/google/skywater-pdk
- sifar 5y agoFor high performance, HW accelerators would gain traction as that would allow them to protect the IP and provide differentiation.
- ThrowawayR2 5y ago> "For cheap, commoditized stuff, open is better than closed for everyone." Having an open core is only half the battle. Cheap, commoditized stuff is tuned and tweaked to within an inch of its life for the available foundries and specific processes on which it is being fabbed both to squeeze out maximum yield and to give the highest possible performance at minimum power. That's very expensive engineering for which investors are going to want to earn their money back on.
- cleemens 5y ago"As should be obvious by now, there is no situation where these foundry processes and tools are open source." This is already false. The famous OpenPDK by Skywater (sponsored by Google) is proving this article wrong from the beginning. (https://github.com/google/skywater-pdk https://github.com/google/skywater-pdk) Yes, thats a rather old technology node, but you can now synthesize your free RISC-V design with a free Toolchain (openROAD) onto this open PDK. Amazing times!
- zozbot234 5y agoThat process node is not just "rather old", it is literally 20 years old. Sure, it's nice that these old processes are being opened up, but for anything finer you're still going to run into the patent concerns that the article talks about.
- makapuf 5y agosure, but having the ability to have an open 1GHz Athlon XP (with increases in IPC allowed by modern architectures) would be nothing to sneeze at. See https://en.wikipedia.org/wiki/130_nm_process https://en.wikipedia.org/wiki/130_nm_process
- klelatti 5y agoCan someone explain why the RISC-V ecosystem won’t eventually stabilise into a series of lower performance open source cores and higher performance closed source (and non licensable) cores. In other words why should designers open source performance leading cores for competitors to copy?
- zrm 5y agoYou're Netgear or Asus or someone. You need a core to put in your network equipment, and the low performance one is nearly good enough. If you spend some money to make it 10% better then it is good enough. If that amount of money is less than you'd have to pay to license ARM, you might as well do that. You also might as well release your changes. If you try and keep your improvements to yourself then when someone else goes to make their own improvements, they start with the original design instead of yours. To get the benefit of their improvements you now have to do more work yourself in order to integrate them with yours. How does that help you? Think about how Linux works. If you release it for anyone to use, when someone else wants to make independent improvements, they start with your design and you get the benefit of their work for free (and vice versa). And you make your money selling routers/phones/coffee machines/whatever, not processors, so this is in your interest. Several iterations of this later and the "higher performance closed source (and non licensable) cores" are starting to look like HP-UX and AIX, meanwhile Linux has captured nearly the entire market.
- klelatti 5y agoThe key point you’ve missed is that Linux is gpl licensed. If you make changes and make those changes available in a binary you have to release the source code. Not so for a new RISC-V core (or notably for many of Linux’s competitors). Sure if you make a small change then you might release it. Designing cores isn’t all about small incremental changes though. Still not sure what the incentives are for a firm that has made a significant investment in a new core or in extending an existing core, what the incentive is for them to release those changes.
- floatboth 5y ago