svn commit: r50090 - head/en_US.ISO8859-1/htdocs/news/status

Mon Mar 27 03:52:38 UTC 2017

Author: bjk
Date: Mon Mar 27 03:52:36 2017
New Revision: 50090
URL: https://svnweb.freebsd.org/changeset/doc/50090

Log:
  Add 2017Q1 s390x entry from bz

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
==============================================================================

--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml	Sun Mar 26 22:11:05 2017	(r50089)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml	Mon Mar 27 03:52:36 2017	(r50090)
@@ -148,4 +148,50 @@
 	via the po system.</task>
     </help>
   </project>
+
+  <project cat='arch'>
+    <title>&os; s390x attempt III</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Bjoern A.</given>
+	  <common>Zeeb</common>
+	</name>
+	<email>bz at FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <body>
+      <p>A long time ago, in the &os; 5 times, there was an initial
+	port of &os; to s390 (32bit) and s390x (64bit)
+	which booted past init on good days in an emulator.</p>
+
+      <p>As an attempt to revive the s390x/systemz efforts I started
+	to get &os; s390x to build with clang/llvm 3.90.
+	At this time it is possible to build world and a GENERIC kernel
+	skeleton (not doing anything yet) using external binutils.</p>
+
+      <p>The primary idea of this initial work was to allow to
+	incrementally add the neccessary architecture-specific code.
+	Having the build framework done will allow third-party
+	developers to simply type <tt>make</tt>, as they are willing
+	to contribute to the port without having to know &os; build
+	specifics.  After some cleanup and further updates to a more
+	recent HEAD I am planning to push the current work to a public
+	repo to allow collaboration.</p>
+    </body>
+
+    <help>
+      <task>Write a wiki page with per-architecture specific tasks
+	that need to be done based on the current work and the experience
+	from arm64 and riscv.</task>
+
+      <task>Implement both the user space and kernel per-architecture
+	gaps.</task>
+
+      <task>Figure out a way to get access to IBM's zPDT or better
+	emulators to ease implementation, testing, and debugging.</task>
+    </help>
+  </project>
 </report>
