6 ms·
Digging into RISC-V and how I learn new things
- mothamikafon 8y agoAmazing how this person understands so little about computers yet is killing it in the first-world job market with her amazing credentials and inclusion into high societies since whenever. Yet here I am, having read every computer architecture book under then sun and contributed to systems that even allow such people to get paid in the first place but still can't get out of this third-world hellhole cuz it's a breeding ground for terrorists. That should be even more reason to help me leave but your collective asses decided that I'm better off around damn dirty muslims.
- eBombzor 8y agoWhat the ..? Would report this if I could.
- mothamikafon 8y agoI have tried everything. This is my last avenue before I die - yelling at wind and getting banned.
- person_of_color 8y agoTo the OP, why are you taking it so personally.
- ribalda 8y agoUnfortunately, 1000 eur is stil a lot for a toy :(. I am sure that the day that they can deliver a 400EUR board the number of developers will explote.
- jessfraz 8y agoThis one is 59 american dollars... https://www.sifive.com/boards/hifive1 https://www.sifive.com/boards/hifive1 hope that helps!
- throwaway_se099 8y agoA lot of developers can surely get by with a QEMU RISC-V image, which exists and is known to boot at least Fedora.
- tverbeure 8y agoHere's how I got my feet wet with RISC-V, for next to nothing: - I bought a cheap FPGA board. Pretty much anything is large enough for a low performance RISC-V CPU. - I added a small design with a picorv32 CPU and experimented with that first. - I designed my own little RISC-V CPU. I've designed digital hardware for decades, and I've learned all about CPUs in college etc, it was still eye opening to actually design one myself. - I write blog posts about all the hobby stuff that I do now. I never did that before, and I'm not looking for a large audience or anything. But what I discovered is that I learn way more about a subject when I write about it: a major part of it is that I want to avoid public embarrassment about writing something wrong. :-) By writing about it, I have to understand things better than when I don't. This may not be the best route for those who don't already have a hardware background, but there are various open source tools now with make it accessible to hobbyists as well. It's been a very fun journey.
- bogomipz 8y ago>"I write blog posts about all the hobby stuff that I do now." What is your blog? I would be interested in reading how you designed your own RISC-V chip. >"This may not be the best route for those who don't already have a hardware background, but there are various open source tools now with make it accessible to hobbyists as well." Can you recommend some of those open source tools that would aid in learning for people who don't already have hardware backgrounds?
- tverbeure 8y agoHere you go: http://tomverbeure.github.io http://tomverbeure.github.io This one is specifically about the RISC-V core: https://tomverbeure.github.io/risc-v/2018/11/19/A-Bug-Free-RISC-V-Core-without-Simulation.html https://tomverbeure.github.io/risc-v/2018/11/19/A-Bug-Free-R... > Can you recommend some of those open source tools that would aid in learning for people who don't already have hardware backgrounds? I haven't played with them myself, but LiteX and FuseSoC are things to look into. There is now also a whole fully open source tool suite to go from RTL (Verilog) all the way to a compiled bitstream for Lattice iCE40 and ECP5 FPGAs. That's not necessarily for beginners though.
- mshockwave 8y agoTraditionally GPU will not classified as VLIW
- monocasa 8y agoGPUs were very much VLIW machines for a while there. The other DSPs that they're hinting at are commonly VLIW machines too.
- bogomipz 8y agoI'm curious was there some inflection point at which GPUs stopped being VLIW machines? I'd be curious to hear when and why that was. Thanks.
- mastax 8y agohttps://www.anandtech.com/show/4455/amds-graphics-core-next-preview-amd-architects-for-compute/2 https://www.anandtech.com/show/4455/amds-graphics-core-next-...
- CalChris 8y ago> Alpha is a great example of an ISA being pretty obsolete outside of owning an old DEC computer Actually, that isn't the case. The Chinese Sunway is based on the Alpha 21164 [1]. The Sunway TaihuLight is 3rd on the supercomputer list [2]. [1] https://en.wikipedia.org/wiki/Sunway_(processor) https://en.wikipedia.org/wiki/Sunway_(processor) [2] https://www.top500.org/lists/2018/11/ https://www.top500.org/lists/2018/11/ (In fact, the Sunway SW26010 has moved on from the Alpha but is still heavily inspired by it.) As for RISC-V itself, I'd be interested in a comparison article between RISC-V and Cray. I think Seymour Cray came up with most good RISC ideas long before Patterson+Ditzel. Indeed, RISC-V is now basing their vector extension on ... Cray. RISC-V as an open source ISA/implementation is one thing. But as a collection of ideas it is another. What ideas distinguish RISC-V from Cray? My personal take is that RISC-V is RISC without the architectural warts of its predecessor RISCs. No register windowing, no tagged integers, no branch delay slot, .... Less is good. But what does RISC-V add that distinguishes it from Cray?
- jessfraz 8y agowow I had no idea thanks!
- bogomipz 8y agoIt seems like there is quite a gap between the Cray's RISC based hardware which I believe were very successful and the introduction of Sun SPARC hardware. Could you or anyone else comment on the reason for this? Was it simply the arrival of research funding from DARPA at Berkeley/Standford in this area?
- CalChris 8y agoBerkeley RISC and Stanford MIPS are circa 1980. I think the enabling factor for them was the availability of fab resources. The RISC-1 had 44,500 transistors. In 1980, Berkeley could get that fabbed for really not much dinero. So it wasn't the funding per se. It was the reduction of fab costs to something they could get funded. Same with the Stanford Geometry Engine. Call it the Carver Mead revolution. The CRAY-1 is 1975. The IBM 801 is 1980 (started in 1975). SPARC comes along in 1987. So I don't think it was the funding. I really think it was the availability of cheap fabs for small tapeouts. The Cray-1 was announced in 1975 and shipped in 1976. IBM took 5 years. It reminds me of the IBM memo all over again: https://www.computerhistory.org/revolution/supercomputers/10/33/62 https://www.computerhistory.org/revolution/supercomputers/10... To which Cray responded, “It seems like Mr. Watson has answered his own question.” Arguably, Berkeley and Stanford's research groups were a lot more like Cray's team.
- gumby 8y ago> were discussing how we learn new things If you're interested in the meta process I highly recommend Polya's "how to solve it" which is full of heuristics for problem solving which are often also about understanding the thing you're trying to solve, i.e. learning!
- person_of_color 8y agoHow does this compare to the Coursera course Learning How to Learn?
- gumby 8y agoIt’s designed for problem solving. Plus you get to read a book instead of having to watch a video.
- analognoise 8y agoI'm actually more interested in having MIPS go open source than I am in RISC-V. It's complete, hardware is extant, and the tooling is mature. I'm really, really hoping the MIPS Open initiative doesn't miss the boat.
- ZirconiumX 8y agoSo, I consider myself a MIPS fan, having studied the early (SGI era) MIPS revisions, but if I started from a clean sheet, I would pick RISC-V over MIPS, because while MIPS is a fairly clean architecture, RISC-V is cleaner. For example, the MIPS R4000 CPU had three microarchitectural branch delay slots of which the latter two had to be cancelled, and that must have been awkward to design. In contrast, RISC-V has no ISA branch delay slots, so requires less from lower-end implementations, and provides more to higher-end out-of-order CPUs.
- analognoise 8y agoThe OpenMIPS initiative is targeting the 32 and 64-bit MIPS Instruction Set Architecture, Release 6 - I'm unsure if the branch delay slot mess is present in it. Hopefully someone can chime in with the answer.