From b092ffbcbe2c9398494f7dc9db6f0796971633e0 Mon Sep 17 00:00:00 2001
From: Rob Austein <sra@hactrn.net>
Date: Sun, 13 Sep 2020 23:04:30 +0000
Subject: Import Cryptech wiki dump

---
 raw-wiki-dump/GitRepositories%2Freleng%2Fnovena | 55 +++++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 raw-wiki-dump/GitRepositories%2Freleng%2Fnovena

(limited to 'raw-wiki-dump/GitRepositories%2Freleng%2Fnovena')

diff --git a/raw-wiki-dump/GitRepositories%2Freleng%2Fnovena b/raw-wiki-dump/GitRepositories%2Freleng%2Fnovena
new file mode 100644
index 0000000..80c1202
--- /dev/null
+++ b/raw-wiki-dump/GitRepositories%2Freleng%2Fnovena
@@ -0,0 +1,55 @@
+{{{
+#!htmlcomment
+
+This page is maintained automatically by a script.  Don't modify this page by hand,
+your changes will just be overwritten the next time the script runs.  Talk to your
+Friendly Neighborhood Repository Maintainer if you need to change something here.
+
+}}}
+
+{{{
+#!html
+<h1>relenv/novena</h1>
+
+<p><strong>WARNING:</strong> Code for the Novena is no longer our primary development
+focus, so while there's no particular reason why recent versions of
+the base code should not work on the Novena, this has not been tested.
+Don't expect frequent updates to this repository.</p>
+
+<p>Release engineering tree for the Cryptech code for the Novena PVT-1,
+initially targetted at what we need to package for IETF 93 in Praha.</p>
+
+<p>General idea is to build two binary packages, one with the bitstream
+for the FPGA, one for software cross-compiled for the Novena.  As a
+convenience, there's also a meta-package which just pulls in the first
+two as dependencies.</p>
+
+<p>The current build setup is somewhat specific to the Novena (in
+particular, the use of the Debian package system), but the general
+outline will likely be reusable for other platforms in the future.</p>
+
+<p>Overall structure of the current setup:</p>
+
+<ul>
+<li><p>The top-level Makefile controls the overall build process.  It does
+_not_ run make directly on any of its subdirectories, instead it
+invokes the Debian package building tools with the right settings.</p></li>
+<li><p>Each of the three packages generated has its own Makefile and
+debian/ directory.  These Makefiles are intended to work with the
+Debian package building tools, and do not necessarily do anything
+useful if used in any other context.</p></li>
+<li><p>Building the software package requires a cross-compiler, see
+<a href="https://wiki.debian.org/CrossToolchains">the Debian cross compilation tools page</a>.</p></li>
+<li><p>Building the firmware package requires
+<a href="http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/design-tools.html">the XiLinx tools</a>.</p></li>
+<li><p>You'll also need the usual Debian package building tools, as well as
+Python and the python-yaml library.</p></li>
+<li><p>The software and Verilog repositories are spliced into this one
+using git's submodule mechanism.  The top-level Makefile attempts to
+automate all of the submodule voodoo needed for normal builds.</p></li>
+</ul>
+}}}
+
+[[RepositoryIndex(format=table,glob=releng/novena)]]
+
+|| Clone `https://git.cryptech.is/releng/novena.git` ||
-- 
cgit v1.2.3