Update external groups.

[riscv-talks.git] / 2016-redhat / notes.txt

diff --git a/2016-redhat/notes.txt b/2016-redhat/notes.txt
index 5ea3c55..6e36acb 100644 (file)
--- a/2016-redhat/notes.txt
+++ b/2016-redhat/notes.txt
@@ -17,13 +17,14 @@ compressed instructions extension
 32 general purpose registers
 32 floating point registers (extension)
 zero register
+always little-endian
 influenced by MIPS
 proven to be patent-free
 
 Boring:
 
 Micro-architecture independent as far as possible
-Micro-op fusion
+Macro-op fusion
 No register windows, branch delay slots etc
 Royalty free, no licensing
 
@@ -61,14 +62,76 @@ Missing bits:
   much of this is filled in with proprietary "IP"
   "Minion cores"
 
+Virtualization
+  Bonzini
+
+What else goes into a server?
+  BMC management
+  standard boot environment (like SBBR on ARM)
+  &c
+
 ----------------------------------------------------------------------
 
+Fedora -- Demo
+
 Fedora
+  Explain why:
+    Current software is crap
+    Busybox
+    Cross-compilers
+    Basically an embedded system
+
+Aims
+
+Scope
+
+Four stage bootstrap process
+  Stage 3 is a "hack job" containing a mix of cross-compiled
+  packages built on the host, layered with "--nodeps"-installed RPMs on top.
+
+  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
+
+  Lots of momentum.  Considerably more realistic than previous
+  open ISA efforts.
+
+  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