<h1>What is RISC-V?</h1>
<blockquote>
-<i>“[RISC-V]'s not supposed to be "different from other architectures".
+<i><q>[RISC-V]'s not supposed to be "different from other architectures".
It's supposed to be as familiar as possible to compiler writers and
CPU designers, minimizing novelty and surprises and maximizing
-precedent so that it can become the <b>Standard Boring ISA</b>.”</i> <br/>
+precedent so that it can become the <b>Standard Boring ISA</b>.</q></i> <br/>
</blockquote>
<p style="text-align: right; margin-right: 3em;">
— Stefan O'Rear on <a href="https://groups.google.com/a/groups.riscv.org/forum/#!forum/isa-dev">the isa-dev mailing list</a>
--- /dev/null
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
+<link rel="stylesheet" href="style.css" type="text/css"/>
+<script src="code.js" type="text/javascript"></script>
+
+<h1>Software development and community</h1>
+
--- /dev/null
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
+<link rel="stylesheet" href="style.css" type="text/css"/>
+<script src="code.js" type="text/javascript"></script>
+
+<h1>What does this mean for Red Hat?</h1>
+
--- /dev/null
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
+<link rel="stylesheet" href="style.css" type="text/css"/>
+<script src="code.js" type="text/javascript"></script>
+
+<h1>RISC-V</h1>
+
+<ul>
+<li> Open source ISA, cores, software. <br/>
+ <a href="https://riscv.org">https://riscv.org</a> <br/>
+ <a href="https://en.wikipedia.org/wiki/RISC-V">https://en.wikipedia.org/wiki/RISC-V</a>
+<li> Supported as a Fedora <q>experimental architecture</q>. <br/>
+ <a href="https://fedoraproject.org/wiki/Architectures/RISC-V">https://fedoraproject.org/wiki/Architectures/RISC-V</a>
+<li> Some years away from general availability of hardware.
+</ul>
Demo
Aims
- Explain why: current software is crap
- Busybox
- Almost like an embedded system
+ Explain why:
+ Current software is crap
+ Busybox
+ Cross-compilers
+ Basically an embedded system
Scope
Stage 4 is the clean image built entirely from RPMs, with all
dependencies satisfied and all files controlled by RPM.
+ The bootstrap process has generally speaking been quite easy (just
+ tedious and slow because it all happens under emulation).
+
+ All the complicated bits (ie. kernel, toolchain) were done already
+ upstream and there haven't been any packages that were difficult to
+ get working.
+
----------------------------------------------------------------------
-Software development and the community
+RISC-V software development and the community
+
+ Friendly and helpful upstream community.
+
+ Far too many of non-upstream forks around.
+
+ Some concerns about changes/instability in the architecture, but
+ at least for userspace things seem pretty solid.
+
+ Really needs virtio support. Someone from the Fedora community
+ is looking into this.
+
+ Fedora community have been very active with packaging.
----------------------------------------------------------------------
-Red Hat
+What does this mean for Red Hat?
+
+
+Summary and questions