From: Richard W.M. Jones <rjones@redhat.com>
Date: Thu, 15 Sep 2016 20:58:43 +0000 (+0100)
Subject: Add end part.
X-Git-Url: http://git.annexia.org/?p=riscv-talks.git;a=commitdiff_plain;h=0e619fa4974cb839b603ba958431c688c84535d1

Add end part.
---

diff --git a/2016-redhat/2020-boring.html b/2016-redhat/2020-boring.html
index 6da920b..3de940a 100644
--- a/2016-redhat/2020-boring.html
+++ b/2016-redhat/2020-boring.html
@@ -5,10 +5,10 @@
 <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;">
 &mdash; Stefan O'Rear on <a href="https://groups.google.com/a/groups.riscv.org/forum/#!forum/isa-dev">the isa-dev mailing list</a>
diff --git a/2016-redhat/4000-community.html b/2016-redhat/4000-community.html
new file mode 100644
index 0000000..cc6bb96
--- /dev/null
+++ b/2016-redhat/4000-community.html
@@ -0,0 +1,6 @@
+<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>
+
diff --git a/2016-redhat/5000-red-hat.html b/2016-redhat/5000-red-hat.html
new file mode 100644
index 0000000..a3a597a
--- /dev/null
+++ b/2016-redhat/5000-red-hat.html
@@ -0,0 +1,6 @@
+<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>
+
diff --git a/2016-redhat/9000-end.html b/2016-redhat/9000-end.html
new file mode 100644
index 0000000..f8a97c5
--- /dev/null
+++ b/2016-redhat/9000-end.html
@@ -0,0 +1,14 @@
+<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>
diff --git a/2016-redhat/notes.txt b/2016-redhat/notes.txt
index f169c6d..0fbc496 100644
--- a/2016-redhat/notes.txt
+++ b/2016-redhat/notes.txt
@@ -69,9 +69,11 @@ Fedora
 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
 
@@ -82,10 +84,32 @@ Four stage bootstrap process
   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