Recent changes to this wiki:

Audio codec is supported on sun7i (same as sun4i)
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- wikisrc/ports/evbarm/allwinner.mdwn	13 Nov 2017 14:44:47 -0000	1.76
+++ wikisrc/ports/evbarm/allwinner.mdwn	18 Nov 2017 18:32:37 -0000	1.77
@@ -56,7 +56,7 @@
     </tr>
   </thead>
   <tbody>
-    <tr><td>Audio codec</td><td>Yes</td><td>Supported on sun4i, sun5i, sun6i, sun8i-h2+, sun8i-h3</td></tr>
+    <tr><td>Audio codec</td><td>Yes</td><td>Supported on sun4i, sun5i, sun6i, sun7i, sun8i-h2+, sun8i-h3</td></tr>
     <tr><td>Crypto engine</td><td>-</td><td></td></tr>
     <tr><td>CSI</td><td>-</td><td></td></tr>
     <tr><td>DMA</td><td>Yes</td><td></td></tr>

Move BSDTW 2017 to Past Events.
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/events.mdwn	27 Oct 2017 11:02:30 -0000	1.52
+++ wikisrc/events.mdwn	16 Nov 2017 16:12:11 -0000	1.53
@@ -9,22 +9,6 @@
 Future Events
 -------------
 
-### `Nov 2017` - BSDTW 2017, Taipei, Taiwan
-
-*November 11 - 12, 2017, Taipei, Taiwan*
-
-[BSDTW 2017](https://bsdtw.org/) is planned as a
-single track, 2 days conference with 11 presentations of 50
-minutes each covering the latest BSD technology. The conference
-will attract over 100 highly skilled engineering professionals,
-software developers, computer science professors, users and
-students from all over Asia as well as other parts of the
-world. The goal of BSDTW is to exchange knowledge about the
-BSD operating systems, facilitate coordination and cooperation
-among users and developers and to promote business friendly
-BSD licensed open source software.
-
-
 ### `Mar 2018` - AsiaBSDCon 2018, Tokyo, Japan
 
 *March 8 - 11, Tokyo University of Science, Tokyo, Japan*
@@ -54,6 +38,22 @@
 Past Events
 -----------
 
+### `Nov 2017` - BSDTW 2017, Taipei, Taiwan
+
+*November 11 - 12, 2017, Taipei, Taiwan*
+
+[BSDTW 2017](https://bsdtw.org/) was planned as a
+single track, 2 days conference with 11 presentations of 50
+minutes each covering the latest BSD technology. The conference
+attracted over 100 highly skilled engineering professionals,
+software developers, computer science professors, users and
+students from all over Asia as well as other parts of the
+world. The goal of BSDTW was to exchange knowledge about the
+BSD operating systems, facilitate coordination and cooperation
+among users and developers and to promote business friendly
+BSD licensed open source software.
+
+
 ### `Sep 2017` - EuroBSDCon 2017 Paris, France
 
 *September 21 - 24, 2017, Paris, France*

NAND flash controller is supported now
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -r1.75 -r1.76
--- wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 21:15:21 -0000	1.75
+++ wikisrc/ports/evbarm/allwinner.mdwn	13 Nov 2017 14:44:47 -0000	1.76
@@ -69,7 +69,7 @@
     <tr><td>I2C</td><td>Yes</td><td></td></tr>
     <tr><td>I2S/PCM</td><td>-</td><td></td></tr>
     <tr><td>IR transceiver</td><td>-</td><td></td></tr>
-    <tr><td>NAND</td><td>-</td><td></td></tr>
+    <tr><td>NAND</td><td>Yes</td><td></td></tr>
     <tr><td>P2WI/RSB</td><td>Yes</td><td></td></tr>
     <tr><td>PWM</td><td>-</td><td></td></tr>
     <tr><td>RTC</td><td>Yes</td><td></td></tr>

Also mention PKGSRC_MKREPRO for building reproducibly
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 15:12:49 -0000	1.37
+++ wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 15:15:48 -0000	1.38
@@ -79,6 +79,18 @@
 PIE executables will only be built for toolchains that are known to support PIE.
 Currently, this means NetBSD on amd64 and i386.
 
+### PKGSRC_MKREPRO
+
+With this option, pkgsrc will try to build packages reproducibly. This allows
+packages built from the same tree and with the same options, to produce
+identical results bit by bit. This option should be combined with ASLR and
+`PKGSRC_MKPIE` to avoid predictable address offsets for attackers attempting to
+exploit security vulnerabilities.
+
+More details can be found here:
+
+* <https://reproducible-builds.org/>
+
 ### PKGSRC_USE_RELRO
 
 This also makes the exploitation of some security vulnerabilities more

Clarify PIE and ASLR a bit more
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 15:02:00 -0000	1.36
+++ wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 15:12:49 -0000	1.37
@@ -67,12 +67,14 @@
 ### PKGSRC_MKPIE
 
 This requests the creation of PIE (Position Independent Executables) for all
-executables. The PIE mechanism is normally used for shared libraries so that
+executables. The PIE mechanism is normally used for shared libraries, so that
 they can be loaded at differing addresses at runtime. PIE itself does not have
-useful security properties.  However, some operating systems support Address
-Space Layout Randomization (ASLR), which causes different addresses to be used
-each time a program is run. This makes it more difficult for an attacker to
-guess addresses and thus makes exploits harder to construct.
+useful security properties; however, it is necessary to fully leverage some,
+such as ASLR.  Some operating systems support Address Space Layout Randomization
+(ASLR), which causes different addresses to be used each time a program is run.
+This makes it more difficult for an attacker to guess addresses and thus makes
+exploits harder to construct. With PIE, ASLR can really be applied to the entire
+program, instead of the stack and heap only.
 
 PIE executables will only be built for toolchains that are known to support PIE.
 Currently, this means NetBSD on amd64 and i386.

Remove extra "the"
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 14:59:14 -0000	1.35
+++ wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 15:02:00 -0000	1.36
@@ -66,14 +66,13 @@
 
 ### PKGSRC_MKPIE
 
-This requests the the creation of PIE (Position Independent
-Executables) for all executables. The PIE mechanism is normally used
-for shared libraries so that they can be loaded at differing addresses
-at runtime. PIE itself does not have useful security properties.
-However, some operating systems support Address Space Layout
-Randomization (ASLR), which causes different addresses to be used each
-time a program is run. This makes it more difficult for an attacker
-to guess addresses and thus makes exploits harder to construct.
+This requests the creation of PIE (Position Independent Executables) for all
+executables. The PIE mechanism is normally used for shared libraries so that
+they can be loaded at differing addresses at runtime. PIE itself does not have
+useful security properties.  However, some operating systems support Address
+Space Layout Randomization (ASLR), which causes different addresses to be used
+each time a program is run. This makes it more difficult for an attacker to
+guess addresses and thus makes exploits harder to construct.
 
 PIE executables will only be built for toolchains that are known to support PIE.
 Currently, this means NetBSD on amd64 and i386.

Mention the check for SSP
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:38:59 -0000	1.34
+++ wikisrc/pkgsrc/hardening.mdwn	12 Nov 2017 14:59:14 -0000	1.35
@@ -289,3 +289,6 @@
     0000000000600ea0 B __stack_chk_guard
 
 This is an indicator that the program was indeed built with support for SSP.
+
+This check is now performed automatically (where supported) if `PKG_DEVELOPER`
+is set and `SSP` is enabled.

Fix the markup
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:37:43 -0000	1.33
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:38:59 -0000	1.34
@@ -44,6 +44,7 @@
 and therefore exposing these bugs.
 
 Different mitigation levels are available:
+
 * the default ("yes"), which will only protect functions considered vulnerable
   by the compiler;
 * "all", which will protect every function;
@@ -56,6 +57,7 @@
 It is enabled by default where known supported since pkgsrc-2017Q3.
 
 More details can be found here:
+
 * <https://en.wikipedia.org/wiki/Buffer_overflow_protection>
 
 ## Enabled by default in pkgsrc HEAD
@@ -82,6 +84,7 @@
 difficult in some cases.
 
 Two different mitigation levels are available:
+
 * partial: the ELF sections are reordered so that internal data sections
   precede the program's own data sections, and non-PLT GOT is read-only;
 * full: in addition to partial RELRO, every relocation is performed immediately
@@ -92,6 +95,7 @@
 feature by default, at the "partial" level.
 
 More details can be found here:
+
 * <http://tk-blog.blogspot.co.at/2009/02/relro-not-so-well-known-memory.html>
 
 ### PKGSRC_USE_STACK_CHECK

Clarify RELRO
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:26:54 -0000	1.32
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:37:43 -0000	1.33
@@ -55,6 +55,7 @@
 
 It is enabled by default where known supported since pkgsrc-2017Q3.
 
+More details can be found here:
 * <https://en.wikipedia.org/wiki/Buffer_overflow_protection>
 
 ## Enabled by default in pkgsrc HEAD
@@ -80,12 +81,18 @@
 This also makes the exploitation of some security vulnerabilities more
 difficult in some cases.
 
-TODO: Explain gcc vs clang, and whether this has broad support or just
-a few platforms.
+Two different mitigation levels are available:
+* partial: the ELF sections are reordered so that internal data sections
+  precede the program's own data sections, and non-PLT GOT is read-only;
+* full: in addition to partial RELRO, every relocation is performed immediately
+  when starting the program (with a slight performance impact), allowing the
+  entire GOT to be read-only.
 
-TODO: Address "partial" vs "full"; which is this?
+This is currently supported by GCC. Many software distributions now enable this
+feature by default, at the "partial" level.
 
-TODO: Give a link to a comprehensive explanation.
+More details can be found here:
+* <http://tk-blog.blogspot.co.at/2009/02/relro-not-so-well-known-memory.html>
 
 ### PKGSRC_USE_STACK_CHECK
 
@@ -278,8 +285,3 @@
     0000000000600ea0 B __stack_chk_guard
 
 This is an indicator that the program was indeed built with support for SSP.
-
-# References
-
-* <http://tk-blog.blogspot.co.at/2009/02/relro-not-so-well-known-memory.html>
-

Add some flesh to PKGSRC_USE_STACK_CHECK
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:22:50 -0000	1.31
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:26:54 -0000	1.32
@@ -89,8 +89,11 @@
 
 ### PKGSRC_USE_STACK_CHECK
 
-This uses `-fstack-check` with GCC for another stack protection
-mitigation.
+This uses `-fstack-check` with GCC for another stack protection mitigation.
+
+It asks the compiler to generate code verifying that it does not corrupt the
+stack. According to GCC's manual page, this is really only useful for
+multi-threaded programs.
 
 # Caveats
 

Clarify support for PIE
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:18:46 -0000	1.30
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:22:50 -0000	1.31
@@ -72,9 +72,8 @@
 time a program is run. This makes it more difficult for an attacker
 to guess addresses and thus makes exploits harder to construct.
 
-TODO/check: PIE executables will only be built for toolchains that
-support PIE and operating systems known to support ASLR. Currently,
-this means NetBSD 8 and later, i386 and amd64.
+PIE executables will only be built for toolchains that are known to support PIE.
+Currently, this means NetBSD on amd64 and i386.
 
 ### PKGSRC_USE_RELRO
 

List the mitigation levels for PKGSRC_USE_SSP
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:14:50 -0000	1.29
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:18:46 -0000	1.30
@@ -43,6 +43,12 @@
 the meantime. This can happen in case of buffer overflows or memory corruption,
 and therefore exposing these bugs.
 
+Different mitigation levels are available:
+* the default ("yes"), which will only protect functions considered vulnerable
+  by the compiler;
+* "all", which will protect every function;
+* "strong", which will apply a better balance between the two settings above.
+
 This mitigation is supported by both GCC and clang. It may be supported in
 additional compilers, possibly under a different name. It is particularly useful
 for unsafe programming languages, such as C/C++.

Add more details for PKGSRC_USE_SSP
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:00:44 -0000	1.28
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:14:50 -0000	1.29
@@ -36,13 +36,21 @@
 
 ### PKGSRC_USE_SSP
 
-This enables a stack-smashing protection mitigation.
-
-TODO: Give a link to a good explanation. Explain if this is gcc
-specific or also works with other compilers. Explain if it is C/C++ only.
+This enables a stack-smashing protection mitigation. It is done by adding a
+guard variable to functions with vulnerable objects. The guards are initialized
+when a function is entered and then checked when the function exits. The guard
+check will fail and the program forcibly exited if the variable was modified in
+the meantime. This can happen in case of buffer overflows or memory corruption,
+and therefore exposing these bugs.
+
+This mitigation is supported by both GCC and clang. It may be supported in
+additional compilers, possibly under a different name. It is particularly useful
+for unsafe programming languages, such as C/C++.
 
 It is enabled by default where known supported since pkgsrc-2017Q3.
 
+* <https://en.wikipedia.org/wiki/Buffer_overflow_protection>
+
 ## Enabled by default in pkgsrc HEAD
 
 ## Not enabled by default

Add a caveat for FORTIFY
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 01:52:37 -0000	1.27
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 02:00:44 -0000	1.28
@@ -136,6 +136,13 @@
 crash, usually indicating an actual bug in the program. The fix will typically
 involve patching the original program.
 
+### Optimization is required
+
+At least in the case of GCC, FORTIFY will only be applied if optimization is
+applied while compiling. This means that the CFLAGS should also contain -O, -O2
+or another optimization level. This cannot easily be applied globally, as some
+packages may require specific optimization levels.
+
 ## Problems with `PKGSRC_USE_RELRO`
 
 ### Performance impact

Typo
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 01:51:03 -0000	1.26
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 01:52:37 -0000	1.27
@@ -8,7 +8,7 @@
 # Mechanisms
 
 Mechanisms can be enabled individually in `mk.conf`, and are
-individually described below. They are sorted by whether thery are
+individually described below. They are sorted by whether they are
 enabled by default, and then by their ordering in `mk/defaults/mk.conf`.
 
 Typically, a feature will cause some programs to fail to build or work

Add markup to a filename
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 01:49:31 -0000	1.25
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 01:51:03 -0000	1.26
@@ -9,7 +9,7 @@
 
 Mechanisms can be enabled individually in `mk.conf`, and are
 individually described below. They are sorted by whether thery are
-enabled by default, and then by their ordering in mk/defaults/mk.conf.
+enabled by default, and then by their ordering in `mk/defaults/mk.conf`.
 
 Typically, a feature will cause some programs to fail to build or work
 when first enabled. This can be due to latent problems in the

Remove doubled spaces
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/pkgsrc/hardening.mdwn	6 Nov 2017 00:04:07 -0000	1.24
+++ wikisrc/pkgsrc/hardening.mdwn	7 Nov 2017 01:49:31 -0000	1.25
@@ -8,12 +8,12 @@
 # Mechanisms
 
 Mechanisms can be enabled individually in `mk.conf`, and are
-individually described below.  They are sorted by whether thery are
+individually described below. They are sorted by whether thery are
 enabled by default, and then by their ordering in mk/defaults/mk.conf.
 
 Typically, a feature will cause some programs to fail to build or work
-when first enabled.  This can be due to latent problems in the
-program, and can be due to other reasons.  After enough testing to
+when first enabled. This can be due to latent problems in the
+program, and can be due to other reasons. After enough testing to
 have confidence that user problems will be quite rare, individual
 mechanisms will be enabled by default.
 
@@ -29,8 +29,8 @@
 library functions that do not have built-in bounds checking - but
 could in some cases.
 
-TODO: Explain FORTIFY_SOURCE 1 vs 2, and which is used.  Give a link
-to a good explanation of the technique.  Explain if this is gcc specific.
+TODO: Explain FORTIFY_SOURCE 1 vs 2, and which is used. Give a link
+to a good explanation of the technique. Explain if this is gcc specific.
 
 It has been enabled by default since pkgsrc-2017Q3.
 
@@ -38,8 +38,8 @@
 
 This enables a stack-smashing protection mitigation.
 
-TODO: Give a link to a good explanation.  Explain if this is gcc
-specific or also works with other compilers.  Explain if it is C/C++ only.
+TODO: Give a link to a good explanation. Explain if this is gcc
+specific or also works with other compilers. Explain if it is C/C++ only.
 
 It is enabled by default where known supported since pkgsrc-2017Q3.
 
@@ -50,16 +50,16 @@
 ### PKGSRC_MKPIE
 
 This requests the the creation of PIE (Position Independent
-Executables) for all executables.  The PIE mechanism is normally used
+Executables) for all executables. The PIE mechanism is normally used
 for shared libraries so that they can be loaded at differing addresses
-at runtime.  PIE itself does not have useful security properties.
+at runtime. PIE itself does not have useful security properties.
 However, some operating systems support Address Space Layout
 Randomization (ASLR), which causes different addresses to be used each
-time a program is run.  This makes it more difficult for an attacker
+time a program is run. This makes it more difficult for an attacker
 to guess addresses and thus makes exploits harder to construct.
 
 TODO/check: PIE executables will only be built for toolchains that
-support PIE and operating systems known to support ASLR.  Currently,
+support PIE and operating systems known to support ASLR. Currently,
 this means NetBSD 8 and later, i386 and amd64.
 
 ### PKGSRC_USE_RELRO

GR8 support landed in 8.99.5
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 17:01:23 -0000	1.74
+++ wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 21:15:21 -0000	1.75
@@ -23,7 +23,7 @@
     <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware">Olimex A10-OLinuXino-LIME</a><td></td></tr>
     <tr><td>sun5i</td><td>A10s</td><td>-</td><td></td></tr>
     <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/open-source-hardware">Olimex A13-OLinuXino</a>, <a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware">Olimex A13-OLinuXino-MICRO</a></td></tr>
-    <tr><td>sun5i</td><td>GR8</td><td>-</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
+    <tr><td>sun5i</td><td>GR8</td><td>8.99.5</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
     <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chip">C.H.I.P.</a>, <a href="https://getchip.com/pages/pocketchip">Pocket C.H.I.P.</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td><a href="http://linux-sunxi.org/Merrii_Hummingbird_A31">Merrii Hummingbird A31</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td><td></td></tr>

GR8 is not supported yet
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -r1.73 -r1.74
--- wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 11:33:30 -0000	1.73
+++ wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 17:01:23 -0000	1.74
@@ -23,7 +23,7 @@
     <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware">Olimex A10-OLinuXino-LIME</a><td></td></tr>
     <tr><td>sun5i</td><td>A10s</td><td>-</td><td></td></tr>
     <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/open-source-hardware">Olimex A13-OLinuXino</a>, <a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware">Olimex A13-OLinuXino-MICRO</a></td></tr>
-    <tr><td>sun5i</td><td>GR8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
+    <tr><td>sun5i</td><td>GR8</td><td>-</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
     <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chip">C.H.I.P.</a>, <a href="https://getchip.com/pages/pocketchip">Pocket C.H.I.P.</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td><a href="http://linux-sunxi.org/Merrii_Hummingbird_A31">Merrii Hummingbird A31</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td><td></td></tr>

add V3s to status table
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -r1.72 -r1.73
--- wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 11:25:43 -0000	1.72
+++ wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 11:33:30 -0000	1.73
@@ -34,6 +34,7 @@
     <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td><a href="http://www.banana-pi.org/m3.html">Sinovoip Banana Pi BPI-M3</a></td><td></td></tr>
     <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td><a href="http://www.orangepi.org/orangepizero/">Xunlong Orange Pi Zero</a></td><td></td></tr>
     <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>
+    <tr><td>sun8i</td><td>V3s</td><td>-</td><td><a href="https://www.indiegogo.com/projects/licheepi-zero-6-extensible-linux-module-on-finger-wifi-diy#/">Lichee Pi Zero</a></td><td></td></tr>
     <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
     <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td>aarch32 mode</td></tr>
     <tr><td>sun50i</td><td>H5</td><td>8.99.4 and later</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2</td><td>aarch32 mode</td></tr>

add A13 and A33 example boards
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- wikisrc/ports/evbarm/allwinner.mdwn	24 Oct 2017 23:48:03 -0000	1.71
+++ wikisrc/ports/evbarm/allwinner.mdwn	6 Nov 2017 11:25:43 -0000	1.72
@@ -22,14 +22,14 @@
   <tbody>
     <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware">Olimex A10-OLinuXino-LIME</a><td></td></tr>
     <tr><td>sun5i</td><td>A10s</td><td>-</td><td></td></tr>
-    <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td></td></tr>
+    <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/open-source-hardware">Olimex A13-OLinuXino</a>, <a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware">Olimex A13-OLinuXino-MICRO</a></td></tr>
     <tr><td>sun5i</td><td>GR8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
     <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chip">C.H.I.P.</a>, <a href="https://getchip.com/pages/pocketchip">Pocket C.H.I.P.</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td><a href="http://linux-sunxi.org/Merrii_Hummingbird_A31">Merrii Hummingbird A31</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td><td></td></tr>
     <tr><td>sun7i</td><td>A20</td><td>7.0 and later</td><td><a href="https://linux-sunxi.org/Cubietech_Cubieboard2">Cubietech Cubieboard 2</a>, <a href="https://linux-sunxi.org/Cubietruck">Cubietech Cubietruck</a>, <a href="http://linux-sunxi.org/LeMaker_Banana_Pi">LeMaker Banana Pi</a></td><td></td></tr>
     <tr><td>sun8i</td><td>A23</td><td>-</td><td></td></tr>
-    <tr><td>sun8i</td><td>A33</td><td>-</td><td></td></tr>
+    <tr><td>sun8i</td><td>A33</td><td>-</td><td><a href="https://www.olimex.com/Products/OLinuXino/A33/A33-OLinuXino/open-source-hardware">Olimex A33-OLinuXino</a></td></tr>
     <tr><td>sun8i</td><td>R40</td><td>-</td><td><a href="http://www.banana-pi.org/m2u.html">Sinovoip Banana Pi BPI-M2U</a></td></tr>
     <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td><a href="http://www.banana-pi.org/m3.html">Sinovoip Banana Pi BPI-M3</a></td><td></td></tr>
     <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td><a href="http://www.orangepi.org/orangepizero/">Xunlong Orange Pi Zero</a></td><td></td></tr>

Add more text
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/pkgsrc/hardening.mdwn	5 Nov 2017 23:54:11 -0000	1.23
+++ wikisrc/pkgsrc/hardening.mdwn	6 Nov 2017 00:04:07 -0000	1.24
@@ -11,9 +11,15 @@
 individually described below.  They are sorted by whether thery are
 enabled by default, and then by their ordering in mk/defaults/mk.conf.
 
-For each, see the Caveats section below for an explanation of what
-might go wrong at compile time and at run time, and how to notice and
-address these problems.
+Typically, a feature will cause some programs to fail to build or work
+when first enabled.  This can be due to latent problems in the
+program, and can be due to other reasons.  After enough testing to
+have confidence that user problems will be quite rare, individual
+mechanisms will be enabled by default.
+
+For each mechanism, see the Caveats section below for an explanation
+of what might go wrong at compile time and at run time, and how to
+notice and address these problems.
 
 ## Enabled by default in the stable branch
 
@@ -61,6 +67,13 @@
 This also makes the exploitation of some security vulnerabilities more
 difficult in some cases.
 
+TODO: Explain gcc vs clang, and whether this has broad support or just
+a few platforms.
+
+TODO: Address "partial" vs "full"; which is this?
+
+TODO: Give a link to a comprehensive explanation.
+
 ### PKGSRC_USE_STACK_CHECK
 
 This uses `-fstack-check` with GCC for another stack protection

Explain more
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/pkgsrc/hardening.mdwn	5 Nov 2017 23:07:27 -0000	1.22
+++ wikisrc/pkgsrc/hardening.mdwn	5 Nov 2017 23:54:11 -0000	1.23
@@ -11,29 +11,60 @@
 individually described below.  They are sorted by whether thery are
 enabled by default, and then by their ordering in mk/defaults/mk.conf.
 
+For each, see the Caveats section below for an explanation of what
+might go wrong at compile time and at run time, and how to notice and
+address these problems.
+
 ## Enabled by default in the stable branch
 
-* `PKGSRC_USE_FORTIFY`: allows substitute wrappers to be used for commonly used
-  functions that do not bounds checking regularly - but could in some cases
-  (enabled by default since pkgsrc-2017Q3)
+### PKGSRC_USE_FORTIFY
+
+This allows substitute wrappers to be used for some commonly used
+library functions that do not have built-in bounds checking - but
+could in some cases.
+
+TODO: Explain FORTIFY_SOURCE 1 vs 2, and which is used.  Give a link
+to a good explanation of the technique.  Explain if this is gcc specific.
+
+It has been enabled by default since pkgsrc-2017Q3.
+
+### PKGSRC_USE_SSP
 
-* 'PKGSRC_USE_SSP`: enables a stack-smashing protection mitigation (enabled
-  by default where known supported since pkgsrc-2017Q3)
+This enables a stack-smashing protection mitigation.
+
+TODO: Give a link to a good explanation.  Explain if this is gcc
+specific or also works with other compilers.  Explain if it is C/C++ only.
+
+It is enabled by default where known supported since pkgsrc-2017Q3.
 
 ## Enabled by default in pkgsrc HEAD
 
 ## Not enabled by default
 
-* `PKGSRC_MKPIE`: forces the creation of PIE (Position Independent
-  Executables) when supported on the current platform.  With PIE
-  executables, a platform that supports ASLR will be able to randomize
-  the process layout.
+### PKGSRC_MKPIE
+
+This requests the the creation of PIE (Position Independent
+Executables) for all executables.  The PIE mechanism is normally used
+for shared libraries so that they can be loaded at differing addresses
+at runtime.  PIE itself does not have useful security properties.
+However, some operating systems support Address Space Layout
+Randomization (ASLR), which causes different addresses to be used each
+time a program is run.  This makes it more difficult for an attacker
+to guess addresses and thus makes exploits harder to construct.
+
+TODO/check: PIE executables will only be built for toolchains that
+support PIE and operating systems known to support ASLR.  Currently,
+this means NetBSD 8 and later, i386 and amd64.
+
+### PKGSRC_USE_RELRO
+
+This also makes the exploitation of some security vulnerabilities more
+difficult in some cases.
 
-* `PKGSRC_USE_RELRO`: this also makes the exploitation of some security
-  vulnerabilities more difficult in some cases.
+### PKGSRC_USE_STACK_CHECK
 
-* `PKGSRC_USE_STACK_CHECK`: uses `-fstack-check` with GCC for another stack
-  protection mitigation.
+This uses `-fstack-check` with GCC for another stack protection
+mitigation.
 
 # Caveats
 

Explain a bit more
Index: wikisrc/pkgsrc/hardening.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/hardening.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/pkgsrc/hardening.mdwn	7 Sep 2017 11:32:21 -0000	1.21
+++ wikisrc/pkgsrc/hardening.mdwn	5 Nov 2017 23:07:27 -0000	1.22
@@ -1,19 +1,37 @@
 [[!meta title="Hardening pkgsrc"]]
 
-A number of mechanisms are available in [pkgsrc](https://www.pkgsrc.org/) to
-improve the security of the resulting system. They can be enabled individually
-in `mk.conf`, and consist of:
+A number of mechanisms are available in
+[pkgsrc](https://www.pkgsrc.org/) to improve the security of the
+resulting system. This page describes the mechanisms, and gives hints
+about detecting and fixing problems.
+
+# Mechanisms
+
+Mechanisms can be enabled individually in `mk.conf`, and are
+individually described below.  They are sorted by whether thery are
+enabled by default, and then by their ordering in mk/defaults/mk.conf.
+
+## Enabled by default in the stable branch
 
-* `PKGSRC_MKPIE`: forces the creation of PIE (Position Independent
-  Executables) when supported on the current platform. This option is necessary
-  to fully leverage ASLR as a mitigation for security vulnerabilities.
 * `PKGSRC_USE_FORTIFY`: allows substitute wrappers to be used for commonly used
   functions that do not bounds checking regularly - but could in some cases
   (enabled by default since pkgsrc-2017Q3)
+
+* 'PKGSRC_USE_SSP`: enables a stack-smashing protection mitigation (enabled
+  by default where known supported since pkgsrc-2017Q3)
+
+## Enabled by default in pkgsrc HEAD
+
+## Not enabled by default
+
+* `PKGSRC_MKPIE`: forces the creation of PIE (Position Independent
+  Executables) when supported on the current platform.  With PIE
+  executables, a platform that supports ASLR will be able to randomize
+  the process layout.
+
 * `PKGSRC_USE_RELRO`: this also makes the exploitation of some security
   vulnerabilities more difficult in some cases.
-* `PKGSRC_USE_SSP`: enables a stack-smashing protection mitigation (enabled
-  by default where known supported since pkgsrc-2017Q3)
+
 * `PKGSRC_USE_STACK_CHECK`: uses `-fstack-check` with GCC for another stack
   protection mitigation.
 

Add blank line before bulleted list
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	28 Oct 2017 00:43:01 -0000	1.65
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	31 Oct 2017 11:32:36 -0000	1.66
@@ -76,6 +76,7 @@
 ### Building yourself
 
 Getting sources and building a release with build.sh is not special for evbarm.  Pick a CPU type alias and pass it to build.sh with -m.  Examples (the first two are equivalent):
+
  - ./build.sh -m earmv6hf -u release
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release

Explain installation more
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -r1.64 -r1.65
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	22 Oct 2017 16:25:18 -0000	1.64
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	28 Oct 2017 00:43:01 -0000	1.65
@@ -55,32 +55,27 @@
 
 ## SD card structure
 
-The Raspberry Pi looks for firmware and a kernel on the first FAT32
-partition of the uSD card.  The NetBSD kernel will then use the FFS
-partition as the root filesystem.
+The Raspberry Pi looks for firmware and kernel.img on the first FAT32 partition of the uSD card.  A separate kernel (kernel7.img) is used on RPI2 and RPI3.
 
-A 2 GB card is the smallest workable size.  The NetBSD filesystem will
-be expanded to fit on larger cards.
+The NetBSD kernel will then use the FFS partition as the root filesystem.
+
+A 2 GB card is the smallest workable size.  The NetBSD filesystem will be expanded to fit.
 
 ## Choosing a version
 
-First, decide if you want to install a formal release (7.1), a stable
-branch build (netbsd-7, netbsd-8), or current.  Note that 7.1 predates
-Raspberry Pi 3 support.  For people who don't know how to choose among
-those, netbsd-8 is probably best.
+First, decide if you want to install a formal release (7.1), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  Note that 7.1 predates Raspberry Pi 3 support.  For people who don't know how to choose among those, netbsd-8 is probably best.
+
+See also "ebijun's image", below, which is NetBSD-current and includes packages.
 
 ## Getting bits to install
 
 You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
 
-Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to
-be written to a uSD card, and has a FAT32 partition for booting.  In
-rpi.img.gz, there is also an FFS partition for NetBSD.
+Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to be written to a uSD card, and has a FAT32 partition for booting.  In rpi.img.gz, there is also an FFS partition for NetBSD.
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.
-Pick a CPU type alias and pass it to build.sh with -m.  Examples:
+Getting sources and building a release with build.sh is not special for evbarm.  Pick a CPU type alias and pass it to build.sh with -m.  Examples (the first two are equivalent):
  - ./build.sh -m earmv6hf -u release
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release
@@ -95,9 +90,9 @@
  - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
  - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
 
-## Installing to uSD
+## Preparing a uSD card
 
-Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for example:
+Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example:
 
  - gunzip rpi.img.gz
  - dd if=rpi.i7mg of=/dev/disk1
@@ -113,9 +108,13 @@
 
    In minicom, run "minicom -s" and set hardware flow control to "no"
 
+### Enabling ssh
+
+If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address, you will have to wait for the partition resizing and reboot.
+
 ### Installation with sshramdisk image
 
-build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  To use this method, write that image to a uSD card as above, and then:
+build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
 
  - Ensure that you have a lan with a DHCP server.
  - Connect an Ethernet cable from the RPI to the LAN.

Add BSDCan 2018 to `Future Events'.
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/events.mdwn	27 Sep 2017 20:32:55 -0000	1.51
+++ wikisrc/events.mdwn	27 Oct 2017 11:02:30 -0000	1.52
@@ -39,6 +39,18 @@
 possible audience.
 
 
+### `Jun 2018` - BSDCan 2018, Ottawa, Canada
+
+*June 6 - 9, 2018, University of Ottawa, Ottawa, Canada*
+
+[BSDCan](https://www.bsdcan.org/2018/), a BSD conference held in
+Ottawa, Canada, quickly established itself as the technical conference
+for people working on and with 4.4BSD based operating systems and
+related projects. The organizers have found a fantastic formula
+that appeals to a wide range of people from extreme novices to
+advanced developers.
+
+
 Past Events
 -----------
 

Add R40 to device table (not currently supported)
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- wikisrc/ports/evbarm/allwinner.mdwn	20 Oct 2017 22:32:20 -0000	1.70
+++ wikisrc/ports/evbarm/allwinner.mdwn	24 Oct 2017 23:48:03 -0000	1.71
@@ -30,6 +30,7 @@
     <tr><td>sun7i</td><td>A20</td><td>7.0 and later</td><td><a href="https://linux-sunxi.org/Cubietech_Cubieboard2">Cubietech Cubieboard 2</a>, <a href="https://linux-sunxi.org/Cubietruck">Cubietech Cubietruck</a>, <a href="http://linux-sunxi.org/LeMaker_Banana_Pi">LeMaker Banana Pi</a></td><td></td></tr>
     <tr><td>sun8i</td><td>A23</td><td>-</td><td></td></tr>
     <tr><td>sun8i</td><td>A33</td><td>-</td><td></td></tr>
+    <tr><td>sun8i</td><td>R40</td><td>-</td><td><a href="http://www.banana-pi.org/m2u.html">Sinovoip Banana Pi BPI-M2U</a></td></tr>
     <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td><a href="http://www.banana-pi.org/m3.html">Sinovoip Banana Pi BPI-M3</a></td><td></td></tr>
     <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td><a href="http://www.orangepi.org/orangepizero/">Xunlong Orange Pi Zero</a></td><td></td></tr>
     <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>

Explain 64-bit RPI3 support future location
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	22 Oct 2017 00:39:08 -0000	1.63
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	22 Oct 2017 16:25:18 -0000	1.64
@@ -41,6 +41,7 @@
 
  - USB (host); isochronous transfers.
  - WiFi
+ - Raspberry Pi 3 in 64-bit mode.  (Note that this will be provided by the evbarm64 port, rather than evbarm.)
 
 # CPU types
 
@@ -48,7 +49,7 @@
 
  - Raspberry Pi 1 uses "earmv6hf".
  - Raspberry Pi 2 uses "earmv7hf".
- - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)
+ - Raspberry Pi 3 uses "earmv7hf".
 
 # Installation
 

Fix explanation of FAT32/FFS.
(The _inst image has no FFS.)
Members: 
	ports/evbarm/raspberry_pi.mdwn:1.62->1.63 

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	22 Oct 2017 00:06:31 -0000	1.62
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	22 Oct 2017 00:39:08 -0000	1.63
@@ -58,6 +58,9 @@
 partition of the uSD card.  The NetBSD kernel will then use the FFS
 partition as the root filesystem.
 
+A 2 GB card is the smallest workable size.  The NetBSD filesystem will
+be expanded to fit on larger cards.
+
 ## Choosing a version
 
 First, decide if you want to install a formal release (7.1), a stable
@@ -70,8 +73,8 @@
 You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
 
 Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to
-be written to a uSD card, and it has a FAT32 partition for booting and
-an FFS partition for NetBSD.
+be written to a uSD card, and has a FAT32 partition for booting.  In
+rpi.img.gz, there is also an FFS partition for NetBSD.
 
 ### Building yourself
 

describe boot partition
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:58:28 -0000	1.61
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	22 Oct 2017 00:06:31 -0000	1.62
@@ -52,6 +52,14 @@
 
 # Installation
 
+## SD card structure
+
+The Raspberry Pi looks for firmware and a kernel on the first FAT32
+partition of the uSD card.  The NetBSD kernel will then use the FFS
+partition as the root filesystem.
+
+## Choosing a version
+
 First, decide if you want to install a formal release (7.1), a stable
 branch build (netbsd-7, netbsd-8), or current.  Note that 7.1 predates
 Raspberry Pi 3 support.  For people who don't know how to choose among

Minor fixes
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:54:22 -0000	1.60
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:58:28 -0000	1.61
@@ -85,7 +85,7 @@
 
 ## Installing to uSD
 
-Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples
+Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for example:
 
  - gunzip rpi.img.gz
  - dd if=rpi.i7mg of=/dev/disk1
@@ -105,7 +105,8 @@
 
 build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  To use this method, write that image to a uSD card as above, and then:
 
- - Connect Ethernet Cable to RPI.
+ - Ensure that you have a lan with a DHCP server.
+ - Connect an Ethernet cable from the RPI to the LAN.
  - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
    - Be careful to note the ip address given during DHCP so you don't lose your connection
    - Also for after the sysinst is done and the system reboots

Add gunzip. Minor formatting fixes
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:52:26 -0000	1.59
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:54:22 -0000	1.60
@@ -87,18 +87,19 @@
 
 Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples
 
- - dd if=rpi.img of=/dev/disk1
+ - gunzip rpi.img.gz
+ - dd if=rpi.i7mg of=/dev/disk1
 
 ### Serial Console
 
 By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then
 edit cmdline.txt and remove '"console=fb"'.
 
-    - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
+ - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
 
-      In Kermit, the command is "set flow none".
+   In Kermit, the command is "set flow none".
 
-      In minicom, run "minicom -s" and set hardware flow control to "no"
+   In minicom, run "minicom -s" and set hardware flow control to "no"
 
 ### Installation with sshramdisk image
 

adjust lists
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:50:25 -0000	1.58
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:52:26 -0000	1.59
@@ -46,9 +46,9 @@
 
 Note that one can also use code for earlier models on later models.
 
-  - Raspberry Pi 1 uses "earmv6hf".
-  - Raspberry Pi 2 uses "earmv7hf".
-  - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)
+ - Raspberry Pi 1 uses "earmv6hf".
+ - Raspberry Pi 2 uses "earmv7hf".
+ - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)
 
 # Installation
 
@@ -69,32 +69,32 @@
 
 Getting sources and building a release with build.sh is not special for evbarm.
 Pick a CPU type alias and pass it to build.sh with -m.  Examples:
-    - ./build.sh -m earmv6hf -u release
-    - ./build.sh -m evbarm -a earmv6hf -u release
-    - ./build.sh -m evbarm -a earmv7hf -u release
+ - ./build.sh -m earmv6hf -u release
+ - ./build.sh -m evbarm -a earmv6hf -u release
+ - ./build.sh -m evbarm -a earmv7hf -u release
 
 ### NetBSD FTP servers
 
 NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
 
-    - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
-    - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2.
-    - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
-    - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
-    - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
+ - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
+ - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2.
+ - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
+ - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
+ - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
 
 ## Installing to uSD
 
 Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples
 
-   - dd if=rpi.img of=/dev/disk1
+ - dd if=rpi.img of=/dev/disk1
 
 ### Serial Console
 
 By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then
 edit cmdline.txt and remove '"console=fb"'.
 
-   - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
+    - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
 
       In Kermit, the command is "set flow none".
 

Update installation instructions and discuss 7/8/current.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 22:51:21 -0000	1.57
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 23:50:25 -0000	1.58
@@ -52,20 +52,47 @@
 
 # Installation
 
- - The automatic nightly builds  on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/) provide image files that can be used for installation. The Raspberry Pi and Pi 2 ports are part of the NetBSD 7 release.
+First, decide if you want to install a formal release (7.1), a stable
+branch build (netbsd-7, netbsd-8), or current.  Note that 7.1 predates
+Raspberry Pi 3 support.  For people who don't know how to choose among
+those, netbsd-8 is probably best.
+
+## Getting bits to install
+
+You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
+
+Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to
+be written to a uSD card, and it has a FAT32 partition for booting and
+an FFS partition for NetBSD.
+
+### Building yourself
+
+Getting sources and building a release with build.sh is not special for evbarm.
+Pick a CPU type alias and pass it to build.sh with -m.  Examples:
+    - ./build.sh -m earmv6hf -u release
+    - ./build.sh -m evbarm -a earmv6hf -u release
+    - ./build.sh -m evbarm -a earmv7hf -u release
+
+### NetBSD FTP servers
+
+NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
+
     - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
-    - The 'evbarm-earmv7hf/binary/gzimg/' directory, as of August 6th 2015, contains an armv7.img file that is optimized for Raspberry Pi 2.
-    - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201412161700Z/evbarm-earmv6hf/binary/gzimg/)
-    - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201508062150Z/evbarm-earminstv7hf/binary/gzimg/)
-  - You can build your own version of these images using (for example) './build.sh -m evbarm -a earmv6hf -u release', or './build.sh -m evbarm -a earmv7hf -u release'
-   - <i>gunzip and dd</i> this img to your sd card. For example,
+    - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2.
+    - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
+    - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
+    - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
+
+## Installing to uSD
 
-	   dd if=rpi.img of=/dev/disk1
+Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples
 
- - Using a serial console
-   - By default the rpi.img is set to use the HDMI output; to change to using a serial console first mount rpi.img (it's a FAT filesystem)
+   - dd if=rpi.img of=/dev/disk1
 
-	   edit cmdline.txt and remove '"console=fb"'
+### Serial Console
+
+By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then
+edit cmdline.txt and remove '"console=fb"'.
 
    - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
 
@@ -73,9 +100,10 @@
 
       In minicom, run "minicom -s" and set hardware flow control to "no"
 
-## Installation with sshramdisk image
+### Installation with sshramdisk image
+
+build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  To use this method, write that image to a uSD card as above, and then:
 
- - You may use the  rpi_inst.img.gz file created by an evbarm build.
  - Connect Ethernet Cable to RPI.
  - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
    - Be careful to note the ip address given during DHCP so you don't lose your connection
@@ -84,9 +112,11 @@
 
 ## Installation via ebijun's image
 
-Jun Ebihara provides an install image for Raspberry Pi that includes
-packages.  It is based on NetBSD-current.  This image is typically
-updated every few weeks.
+As an alternative to the standard installation images, Jun Ebihara
+provides an install image for Raspberry Pi that includes packages.  It
+is based on NetBSD-current and is built for earmv6hf, and thus will
+work on Raspberry Pi 1, 2 and 3.  This image is typically updated
+every few weeks.
 
  - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
 

Add cputype information
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 15:08:18 -0000	1.56
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Oct 2017 22:51:21 -0000	1.57
@@ -42,6 +42,14 @@
  - USB (host); isochronous transfers.
  - WiFi
 
+# CPU types
+
+Note that one can also use code for earlier models on later models.
+
+  - Raspberry Pi 1 uses "earmv6hf".
+  - Raspberry Pi 2 uses "earmv7hf".
+  - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)
+
 # Installation
 
  - The automatic nightly builds  on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/) provide image files that can be used for installation. The Raspberry Pi and Pi 2 ports are part of the NetBSD 7 release.

fix wording
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- wikisrc/ports/evbarm.mdwn	21 Oct 2017 22:43:03 -0000	1.43
+++ wikisrc/ports/evbarm.mdwn	21 Oct 2017 22:45:12 -0000	1.44
@@ -29,7 +29,7 @@
 there is hardware floating point.  By default the CPU type is "earm",
 and this implies little endian (el when explicitly stated), and soft
 (emulated) floating point.  Another example, suitable for Raspberry PI
-2, is earmv7hf, which is the v7 instruction support, little endian,
+2, is earmv7hf, which is the v7 instruction set, little endian,
 and hardware floating point.
 
 Typically, various boards are best compiled with a CPU type that

Extend cpu discussion
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- wikisrc/ports/evbarm.mdwn	21 Oct 2017 22:39:47 -0000	1.42
+++ wikisrc/ports/evbarm.mdwn	21 Oct 2017 22:43:03 -0000	1.43
@@ -26,13 +26,23 @@
 
 The evbarm port can be built with a variety of CPU options.  There are
 three main variables: the instruction set, the endianness, and whether
-there is hardware flaoting point.  By default the CPU type is "earm".
+there is hardware floating point.  By default the CPU type is "earm",
+and this implies little endian (el when explicitly stated), and soft
+(emulated) floating point.  Another example, suitable for Raspberry PI
+2, is earmv7hf, which is the v7 instruction support, little endian,
+and hardware floating point.
 
 Typically, various boards are best compiled with a CPU type that
 matches the board's CPU and floating point support, but generally a
 lower CPU instruction set version is workable on a newer board.  See
 build.sh and look for aliases for the evbarm port.
 
+### Kernels and userland
+
+The evbarm userland can be used on any system that can run code of the
+CPU type used for the build.  Typically, a particular board requires a
+kernel for that board.
+
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone and BeagleBone Black|BeagleBone]]

Describe CPU type notion
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/ports/evbarm.mdwn	10 Oct 2017 10:43:51 -0000	1.41
+++ wikisrc/ports/evbarm.mdwn	21 Oct 2017 22:39:47 -0000	1.42
@@ -22,6 +22,17 @@
 
 Matt Thomas is the maintainer of NetBSD/evbarm.
 
+### CPU types
+
+The evbarm port can be built with a variety of CPU options.  There are
+three main variables: the instruction set, the endianness, and whether
+there is hardware flaoting point.  By default the CPU type is "earm".
+
+Typically, various boards are best compiled with a CPU type that
+matches the board's CPU and floating point support, but generally a
+lower CPU instruction set version is workable on a newer board.  See
+build.sh and look for aliases for the evbarm port.
+
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone and BeagleBone Black|BeagleBone]]

Added a comment: doesn't work
--- /dev/null	2017-10-21 14:00:33.000000000 +0000
+++ wikisrc/tutorials/how_to_install_netbsd_on_hpcarm/comment_1_4ccf2cd6224e5e97c2fca71a02944ae7._comment	2017-10-21 14:02:45.000000000 +0000
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/ceCmhGBukoQo3T2YQY9d06pQzt76i4Jp#a1439"
+ nickname="Nigel"
+ subject="doesn't work"
+ date="2017-10-21T14:02:25Z"
+ content="""
+# disklabel -i -I sd0
+disklabel: /dev/rsd0: Device not configured
+
+"""]]

Fast Ethernet (sun4i/sun7i) is supported now
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- wikisrc/ports/evbarm/allwinner.mdwn	11 Oct 2017 10:55:19 -0000	1.69
+++ wikisrc/ports/evbarm/allwinner.mdwn	20 Oct 2017 22:32:20 -0000	1.70
@@ -58,7 +58,7 @@
     <tr><td>Crypto engine</td><td>-</td><td></td></tr>
     <tr><td>CSI</td><td>-</td><td></td></tr>
     <tr><td>DMA</td><td>Yes</td><td></td></tr>
-    <tr><td>Fast Ethernet (sun4i/sun7i)</td><td>-</td><td></td></tr>
+    <tr><td>Fast Ethernet (sun4i/sun7i)</td><td>Yes</td><td></td></tr>
     <tr><td>Framebuffer</td><td>Yes</td><td>Uses simplefb configured by bootloader</td></tr>
     <tr><td>Gigabit Ethernet (sun6i/sun7i/sun9i)</td><td>Yes</td><td></td></tr>
     <tr><td>Gigabit Ethernet (sun8i/sun50i)</td><td>Yes</td><td></td></tr>

Typo
Index: wikisrc/tutorials/pkgsrc/cross_compile_distcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/cross_compile_distcc.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/pkgsrc/cross_compile_distcc.mdwn	22 Feb 2012 21:36:40 -0000	1.4
+++ wikisrc/tutorials/pkgsrc/cross_compile_distcc.mdwn	19 Oct 2017 23:31:44 -0000	1.5
@@ -3,7 +3,7 @@
 You may want to use several machines to speed up your *pkgsrc* builds, but
 as those computers are not running NetBSD, you may think they are useless as
 build-helpers. This is where enters NetBSD's *cross-compiling* system in
-conjuction with [distcc](http://code.google.com/p/distcc/).
+conjunction with [distcc](http://code.google.com/p/distcc/).
 
 ### A classic scenario
 

Remove SCTP from list.
Index: wikisrc/projects/ideas.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/ideas.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/ideas.mdwn	17 Feb 2016 06:32:39 -0000	1.5
+++ wikisrc/projects/ideas.mdwn	17 Oct 2017 19:36:48 -0000	1.6
@@ -43,8 +43,6 @@
 
 1. *difficult* Write new DTrace provider for watching locks(lockdebug), userspace or any other from available ones <http://wikis.sun.com/display/DTrace/Providers>
 
-1. SCTP support
-
 1. Change keyboard drivers to emit USB scancodes in event mode so for example ADB or Sun keyboards can coexist with things like USB keypads on the same mux and we don't need a separate InputDevice section in xorg.conf for each. This should be relatively easy.
 
 1. Port FreeBSD's DAHDI implementation to NetBSD, so that Asterisk on NetBSD will have hardware support.  FreeBSD's DAHDI implementation is SMP, so this isn't a simple port.  Also, just about every FreeBSD kernel API related to device drivers and modules are different from the NetBSD equivalent meaning that one needs to basically know both kernels.

fix link
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 15:06:30 -0000	1.55
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 15:08:18 -0000	1.56
@@ -80,7 +80,7 @@
 packages.  It is based on NetBSD-current.  This image is typically
 updated every few weeks.
 
- - https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README
+ - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
 
 ## Updating the kernel
 

Remove incorporated comment
--- wikisrc/ports/evbarm/raspberry_pi/comment_19_82864947fcb8737650f36e90ed1ed9b8._comment	2017-10-14 15:07:44.000000000 +0000
+++ /dev/null	2017-10-14 15:00:33.000000000 +0000
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UM0fy451yPQ9iZSVKjtjNcPifA--#1f032"
- nickname="Fredrik Pettai"
- subject="Lots of useful info regarding NetBSD on RPI collected by Jun Ebihara"
- date="2017-02-04T20:35:28Z"
- content="""
-See Jun Ebihara's GitHub page where lots of stuff regarding NetBSD on RPI is collected:
-<https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README>
-"""]]

Add link to ebijun's image.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 14:54:58 -0000	1.54
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 15:06:30 -0000	1.55
@@ -48,7 +48,7 @@
     - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
     - The 'evbarm-earmv7hf/binary/gzimg/' directory, as of August 6th 2015, contains an armv7.img file that is optimized for Raspberry Pi 2.
     - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201412161700Z/evbarm-earmv6hf/binary/gzimg/)
-    - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201508062150Z/evbarm-earmv7hf/binary/gzimg/)
+    - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201508062150Z/evbarm-earminstv7hf/binary/gzimg/)
   - You can build your own version of these images using (for example) './build.sh -m evbarm -a earmv6hf -u release', or './build.sh -m evbarm -a earmv7hf -u release'
    - <i>gunzip and dd</i> this img to your sd card. For example,
 
@@ -74,6 +74,14 @@
    - Also for after the sysinst is done and the system reboots
  - sysinst started!
 
+## Installation via ebijun's image
+
+Jun Ebihara provides an install image for Raspberry Pi that includes
+packages.  It is based on NetBSD-current.  This image is typically
+updated every few weeks.
+
+ - https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README
+
 ## Updating the kernel
 
  - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.

demote "what doesn't work" to level 2
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 14:53:46 -0000	1.53
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 14:54:58 -0000	1.54
@@ -10,7 +10,7 @@
 
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
 
-# What works
+# What works (and what doesn't yet)
 
 ## NetBSD 7 before July, 2017
 
@@ -37,7 +37,7 @@
  - Raspberry Pi 3 bluetooth
  - Raspberry Pi 3 new SD host controller driver
 
-# What needs work
+## What needs work
 
  - USB (host); isochronous transfers.
  - WiFi

reorganize to focus more on users
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 23:26:29 -0000	1.52
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	14 Oct 2017 14:53:46 -0000	1.53
@@ -10,7 +10,40 @@
 
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
 
+# What works
+
+## NetBSD 7 before July, 2017
+
+ - RaspberryPi 1, and 2 (including SMP)
+ - multi-user boot with root on SD card
+ - serial or graphics console (with EDID query / parsing)
+ - DMA controller driver and sdhc(4) support
+ - Audio: works. man page missing.
+ - I²C: works, could use enhancements, man page
+ - GPIO
+ - RNG
+ - SPI: could use enhancements, man page
+ - GPU (VCHIQ) - 3D and video decode. man page missing.
+ - USB (host) - dwctwo(4)
+ - USB Ethernet - usmsc(4)
+ - X windows.
+
+## NetBSD 7 after July, 2017 and NetBSD 8
+
+ - Raspberry Pi 3 (excluding WiFi and bluetooth)
+
+## NetBSD current
+
+ - Raspberry Pi 3 bluetooth
+ - Raspberry Pi 3 new SD host controller driver
+
+# What needs work
+
+ - USB (host); isochronous transfers.
+ - WiFi
+
 # Installation
+
  - The automatic nightly builds  on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/) provide image files that can be used for installation. The Raspberry Pi and Pi 2 ports are part of the NetBSD 7 release.
     - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
     - The 'evbarm-earmv7hf/binary/gzimg/' directory, as of August 6th 2015, contains an armv7.img file that is optimized for Raspberry Pi 2.
@@ -32,7 +65,8 @@
 
       In minicom, run "minicom -s" and set hardware flow control to "no"
 
-# Installation with sshramdisk image
+## Installation with sshramdisk image
+
  - You may use the  rpi_inst.img.gz file created by an evbarm build.
  - Connect Ethernet Cable to RPI.
  - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
@@ -40,27 +74,8 @@
    - Also for after the sysinst is done and the system reboots
  - sysinst started!
 
-# Updating the firmware
-
-You probably don't want to do this. Firmware updates can break things,
-and the latest firmware that's been tested is already included in the
-NetBSD build you installed.
-
-If you're feeling adventurous (or are the port maintainer), here's what
-to test whenever you try new firmware:
-
-- Audio
-- OMXPlayer (and [[!template id=man name="vchiq"]])
-- Serial/framebuffer console
-- CPU frequency scaling
-
-That goes for all of `rpi[0123]`.
+## Updating the kernel
 
-Upstream firmware releases are
-[on GitHub](https://github.com/raspberrypi/firmware/releases).
-Copy all files except `kernel*.img` into `/boot` and reboot.
-
-# Updating the kernel
  - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
 
          ...
@@ -73,6 +88,9 @@
  - reboot
 
 # Wireless Networking
+
+  Note that the built-in WiFi in the RPI3 is not yet supported.
+
  - A Realtek 802.11n USB adaptor configures as urtwn(4).
    - Configure with wpa_supplicant in /etc/rc.conf -
 
@@ -115,32 +133,26 @@
 $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
 """]]
 
-# What works
+# Developer notes
 
-## NetBSD 7 before July, 2017
+These notes are for people working on improvements to RPI support in NetBSD.
 
- - RaspberryPi 1, and 2 (including SMP)
- - multi-user boot with root on SD card
- - serial or graphics console (with EDID query / parsing)
- - DMA controller driver and sdhc(4) support
- - Audio: works. man page missing.
- - I²C: works, could use enhancements, man page
- - GPIO
- - RNG
- - SPI: could use enhancements, man page
- - GPU (VCHIQ) - 3D and video decode. man page missing.
- - USB (host) - dwctwo(4)
- - USB Ethernet - usmsc(4)
- - X windows.
+## Updating the firmware
 
-## NetBSD 7 after July, 2017 and NetBSD 8
+You probably don't want to do this. Firmware updates can break things,
+and the latest firmware that's been tested is already included in the
+NetBSD build you installed.
 
- - Raspberry Pi 3 (excluding wifi and bluetooth)
+If you're feeling adventurous (or are the port maintainer), here's what
+to test whenever you try new firmware:
 
-## NetBSD current
+- Audio
+- OMXPlayer (and [[!template id=man name="vchiq"]])
+- Serial/framebuffer console
+- CPU frequency scaling
 
- - Raspberry Pi 3 bluetooth
- - Raspberry Pi 3 new SD host controller driver
+That goes for all of `rpi[0123]`.
 
-# What needs work
- - USB (host); isochronous transfers.
+Upstream firmware releases are
+[on GitHub](https://github.com/raspberrypi/firmware/releases).
+Copy all files except `kernel*.img` into `/boot` and reboot.

Use markdown lists to ease a bit the readability, NFCI.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 04:38:31 -0000	1.21
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 08:24:18 -0000	1.22
@@ -51,13 +51,13 @@
 
 For example, add the following to `/etc/modules.conf` (the file may not exist already on a system):
     
-    solaris
-    dtrace
-    dtrace_sdt
-    dtrace_fbt
-    dtrace_lockstat
-    dtrace_profile
-    dtrace_syscall
+- `solaris`
+- `dtrace`
+- `dtrace_sdt`
+- `dtrace_fbt`
+- `dtrace_lockstat`
+- `dtrace_profile`
+- `dtrace_syscall`
     
 A `dtrace` device node is created automatically in `/dev/dtrace` when the modules are loaded into place.
     
@@ -136,8 +136,8 @@
 
 At present, the following scripts are installed in `/usr/sbin`: 
 
-    dtruss - An implementation of the truss utility in DTrace which traces the system calls
-    made by a process
-    execsnoop - snoop on execution of processes as they occur
-    opensnoop - snoop on openning of files as they occur
-    procsystime -  print process system call time details.
+- `dtruss` - An implementation of the truss utility in DTrace which traces the system calls
+made by a process
+- `execsnoop` - snoop on execution of processes as they occur
+- `opensnoop` - snoop on openning of files as they occur
+- `procsystime` -  print process system call time details.

Remove duplication mistake.
State the path the scripts are installed in.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 04:27:54 -0000	1.20
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 04:38:31 -0000	1.21
@@ -134,7 +134,7 @@
 Starting with NetBSD-8, on builds where `MKDTRACE=yes` is set, scripts from
 [Brendan Gregg's DTrace toolkit](https://github.com/opendtrace/toolkit/) are installed in base as standard.
 
-At present the following scripts are installed are installed:
+At present, the following scripts are installed in `/usr/sbin`: 
 
     dtruss - An implementation of the truss utility in DTrace which traces the system calls
     made by a process

Break up listing to separate lines?
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 04:25:27 -0000	1.19
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 04:27:54 -0000	1.20
@@ -136,8 +136,8 @@
 
 At present the following scripts are installed are installed:
 
-dtruss - An implementation of the truss utility in DTrace which traces the system calls
-made by a process
-execsnoop - snoop on execution of processes as they occur
-opensnoop - snoop on openning of files as they occur
-procsystime -  print process system call time details.
+    dtruss - An implementation of the truss utility in DTrace which traces the system calls
+    made by a process
+    execsnoop - snoop on execution of processes as they occur
+    opensnoop - snoop on openning of files as they occur
+    procsystime -  print process system call time details.

Mention scripts installed from DTrace Toolkit.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	8 Apr 2017 21:38:18 -0000	1.18
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	13 Oct 2017 04:25:27 -0000	1.19
@@ -128,3 +128,16 @@
     
 
 Start the script running (dtrace -s sleep.d) and then execute a "sleep 2" in another shell. 
+
+## Tools included base
+
+Starting with NetBSD-8, on builds where `MKDTRACE=yes` is set, scripts from
+[Brendan Gregg's DTrace toolkit](https://github.com/opendtrace/toolkit/) are installed in base as standard.
+
+At present the following scripts are installed are installed:
+
+dtruss - An implementation of the truss utility in DTrace which traces the system calls
+made by a process
+execsnoop - snoop on execution of processes as they occur
+opensnoop - snoop on openning of files as they occur
+procsystime -  print process system call time details.

H5 is supported now
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- wikisrc/ports/evbarm/allwinner.mdwn	9 Oct 2017 17:00:28 -0000	1.68
+++ wikisrc/ports/evbarm/allwinner.mdwn	11 Oct 2017 10:55:19 -0000	1.69
@@ -35,7 +35,7 @@
     <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>
     <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
     <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td>aarch32 mode</td></tr>
-    <tr><td>sun50i</td><td>H5</td><td>-</td><td></td></tr>
+    <tr><td>sun50i</td><td>H5</td><td>8.99.4 and later</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2</td><td>aarch32 mode</td></tr>
     <tr><td>sun50i</td><td>H6</td><td>-</td><td></td></tr>
   </tbody>
 </table>

Use `pkg' template instead of links to pkgsrc.se, NFCI.
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/ports/evbarm/tegra.mdwn	10 Oct 2017 10:52:21 -0000	1.48
+++ wikisrc/ports/evbarm/tegra.mdwn	11 Oct 2017 08:43:24 -0000	1.49
@@ -29,7 +29,7 @@
  - SDMMC [[!template id=man name="sdhc" section="4"]] controller
  - USB 2.0 [[!template id=man name="ehci" section="4"]] controller
  - USB 3.0 [[!template id=man name="xhci" section="4"]] controller
-   - Requires the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package to be installed.
+   - Requires the [[!template id=pkg category="sysutils" name="tegra-firmware"]] package to be installed.
  - PCI express
  - SATA [[!template id=man name="ahcisata" section="4"]] controller
  - HDMI
@@ -79,7 +79,7 @@
 
 Jetson TK1 boards come with Linux4Tegra R19.x installed, which doesn't use U-Boot. The easiest way to get U-Boot is to upgrade to Linux4Tegra R21.x (Linux PC or VM required) following the [quick start guide](http://developer.download.nvidia.com/embedded/L4T/r21_Release_v4.0/l4t_quick_start_guide.txt).
 
-U-Boot for Jetson TX1 is available in pkgsrc: [sysutils/u-boot-jetson-tx1](http://pkgsrc.se/sysutils/u-boot-jetson-tx1).
+U-Boot for Jetson TX1 is available in pkgsrc: [[!template id=pkg category="sysutils" name="u-boot-jetson-tx1"]].
 
 # Modesetting
 
@@ -112,7 +112,7 @@
 
 For the nouveau driver to load successfully, firmware is required:
 
-* Install the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package from pkgsrc.
+* Install the [[!template id=pkg category="sysutils" name="tegra-firmware"]] package from pkgsrc.
 * Extract the contents of [tegra-nouveau-firmware.tar.gz](http://cdn.netbsd.org/pub/NetBSD/misc/jmcneill/tegra/tegra-nouveau-firmware.tar.gz) to ''/libdata/firmware/nouveau''.
 
 You should see the following messages at boot:

Add some TX1 info
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- wikisrc/ports/evbarm/tegra.mdwn	31 Jul 2017 17:54:21 -0000	1.47
+++ wikisrc/ports/evbarm/tegra.mdwn	10 Oct 2017 10:52:21 -0000	1.48
@@ -1,6 +1,11 @@
 [[!meta title="NetBSD/evbarm on NVIDIA Tegra"]]
 
-The NetBSD tegra port currently supports the NVIDIA Tegra K1 (32-bit) system-on-a-chip. The [NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1) is a board based on the Tegra K1 SoC.
+NetBSD 8.0 supports the NVIDIA Tegra K1 (32-bit) system-on-a-chip.
+NetBSD -current adds support for the NVIDIA Tegra X1 system-on-a-chip.
+
+The [NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1) is a board based on the Tegra K1 SoC.
+The [NVIDIA Jetson TX1 development kit](https://developer.nvidia.com/jetson-tx1) is a board based on the Tegra X1 SoC.
+
 
 [[!toc levels=2]]
 
@@ -8,6 +13,8 @@
  - CPU: Cortex-A15: NVIDIA Tegra K1 (T124) (4-core)
    - VFP / NEON
    - CPU frequency scaling
+ - CPU: Cortex-A57: NVIDIA Tegra X1 (T210) (4-core)
+   - VFP / NEON
  - GIC
  - ARM generic timer
  - Clock and reset controller
@@ -35,6 +42,8 @@
    - TMP451 [[!template id=man name="titemp" section="4"]] temperature sensor (on I2C)
    - RF kill switch
    - Power button
+ - Jetson TX1
+   - On-board Realtek RTL8153 [[!template id=man name="cdce" section="4"]] gigabit ethernet
  - AS3722 power management unit
  - eFUSE
  - SoC thermal sensors
@@ -70,6 +79,8 @@
 
 Jetson TK1 boards come with Linux4Tegra R19.x installed, which doesn't use U-Boot. The easiest way to get U-Boot is to upgrade to Linux4Tegra R21.x (Linux PC or VM required) following the [quick start guide](http://developer.download.nvidia.com/embedded/L4T/r21_Release_v4.0/l4t_quick_start_guide.txt).
 
+U-Boot for Jetson TX1 is available in pkgsrc: [sysutils/u-boot-jetson-tx1](http://pkgsrc.se/sysutils/u-boot-jetson-tx1).
+
 # Modesetting
 
 ## Console

Jetson TK1 -> Tegra
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/ports/evbarm.mdwn	8 Oct 2017 22:10:55 -0000	1.40
+++ wikisrc/ports/evbarm.mdwn	10 Oct 2017 10:43:51 -0000	1.41
@@ -25,7 +25,7 @@
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone and BeagleBone Black|BeagleBone]]
- - [[NVIDIA Jetson TK1|Tegra]]
+ - [[NVIDIA Tegra|Tegra]]
  - [[ODROID C1 and C1+|ODROID-C1]]
  - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
 

Touch screen controller is supported on all SoCs that have one (AFAICT)
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- wikisrc/ports/evbarm/allwinner.mdwn	9 Oct 2017 16:31:27 -0000	1.67
+++ wikisrc/ports/evbarm/allwinner.mdwn	9 Oct 2017 17:00:28 -0000	1.68
@@ -77,7 +77,7 @@
     <tr><td>SPDIF</td><td>-</td><td></td></tr>
     <tr><td>SPI</td><td>-</td><td></td></tr>
     <tr><td>Thermal sensors</td><td>Yes</td><td></td></tr>
-    <tr><td>Touch screen</td><td>Yes</td><td>Supported on sun4i, sun5i, sun6i</td></tr>
+    <tr><td>Touch screen</td><td>Yes</td><td></td></tr>
     <tr><td>UART</td><td>Yes</td><td></td></tr>
     <tr><td>USB 2.0</td><td>Yes</td><td></td></tr>
     <tr><td>USB OTG</td><td>Experimental</td><td></td></tr>

Updated thermal sensor and touch screen controller info
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -r1.66 -r1.67
--- wikisrc/ports/evbarm/allwinner.mdwn	9 Oct 2017 00:22:28 -0000	1.66
+++ wikisrc/ports/evbarm/allwinner.mdwn	9 Oct 2017 16:31:27 -0000	1.67
@@ -76,8 +76,8 @@
     <tr><td>SMP</td><td>Yes</td><td>Uses PSCI support in firmware</td></tr>
     <tr><td>SPDIF</td><td>-</td><td></td></tr>
     <tr><td>SPI</td><td>-</td><td></td></tr>
-    <tr><td>Thermal sensors</td><td>Yes</td><td>Supported on sun8i-a83t, sun8i-h3, sun50i-a64</td></tr>
-    <tr><td>Touch screen</td><td>Yes</td><td>Supported on sun5i</td></tr>
+    <tr><td>Thermal sensors</td><td>Yes</td><td></td></tr>
+    <tr><td>Touch screen</td><td>Yes</td><td>Supported on sun4i, sun5i, sun6i</td></tr>
     <tr><td>UART</td><td>Yes</td><td></td></tr>
     <tr><td>USB 2.0</td><td>Yes</td><td></td></tr>
     <tr><td>USB OTG</td><td>Experimental</td><td></td></tr>

Add some unsupported hardware
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:54:46 -0000	1.65
+++ wikisrc/ports/evbarm/allwinner.mdwn	9 Oct 2017 00:22:28 -0000	1.66
@@ -55,19 +55,27 @@
   </thead>
   <tbody>
     <tr><td>Audio codec</td><td>Yes</td><td>Supported on sun4i, sun5i, sun6i, sun8i-h2+, sun8i-h3</td></tr>
+    <tr><td>Crypto engine</td><td>-</td><td></td></tr>
+    <tr><td>CSI</td><td>-</td><td></td></tr>
     <tr><td>DMA</td><td>Yes</td><td></td></tr>
     <tr><td>Fast Ethernet (sun4i/sun7i)</td><td>-</td><td></td></tr>
     <tr><td>Framebuffer</td><td>Yes</td><td>Uses simplefb configured by bootloader</td></tr>
     <tr><td>Gigabit Ethernet (sun6i/sun7i/sun9i)</td><td>Yes</td><td></td></tr>
     <tr><td>Gigabit Ethernet (sun8i/sun50i)</td><td>Yes</td><td></td></tr>
     <tr><td>GPIO</td><td>Yes</td><td></td></tr>
+    <tr><td>GPU</td><td>-</td><td></td></tr>
     <tr><td>I2C</td><td>Yes</td><td></td></tr>
+    <tr><td>I2S/PCM</td><td>-</td><td></td></tr>
     <tr><td>IR transceiver</td><td>-</td><td></td></tr>
+    <tr><td>NAND</td><td>-</td><td></td></tr>
     <tr><td>P2WI/RSB</td><td>Yes</td><td></td></tr>
+    <tr><td>PWM</td><td>-</td><td></td></tr>
     <tr><td>RTC</td><td>Yes</td><td></td></tr>
     <tr><td>SATA</td><td>Yes</td><td></td></tr>
     <tr><td>SD/MMC</td><td>Yes</td><td></td></tr>
     <tr><td>SMP</td><td>Yes</td><td>Uses PSCI support in firmware</td></tr>
+    <tr><td>SPDIF</td><td>-</td><td></td></tr>
+    <tr><td>SPI</td><td>-</td><td></td></tr>
     <tr><td>Thermal sensors</td><td>Yes</td><td>Supported on sun8i-a83t, sun8i-h3, sun50i-a64</td></tr>
     <tr><td>Touch screen</td><td>Yes</td><td>Supported on sun5i</td></tr>
     <tr><td>UART</td><td>Yes</td><td></td></tr>

Add RTC and SATA
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -r1.64 -r1.65
--- wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:48:41 -0000	1.64
+++ wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:54:46 -0000	1.65
@@ -64,6 +64,8 @@
     <tr><td>I2C</td><td>Yes</td><td></td></tr>
     <tr><td>IR transceiver</td><td>-</td><td></td></tr>
     <tr><td>P2WI/RSB</td><td>Yes</td><td></td></tr>
+    <tr><td>RTC</td><td>Yes</td><td></td></tr>
+    <tr><td>SATA</td><td>Yes</td><td></td></tr>
     <tr><td>SD/MMC</td><td>Yes</td><td></td></tr>
     <tr><td>SMP</td><td>Yes</td><td>Uses PSCI support in firmware</td></tr>
     <tr><td>Thermal sensors</td><td>Yes</td><td>Supported on sun8i-a83t, sun8i-h3, sun50i-a64</td></tr>

Add a table of supported hardware.
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:31:37 -0000	1.63
+++ wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:48:41 -0000	1.64
@@ -43,7 +43,37 @@
 
 # Supported hardware
 
-Please refer to the [SUNXI kernel config](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/SUNXI) for a list of supported hardware.
+Please refer to the [SUNXI kernel config](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/SUNXI) for the most up-to-date list of supported hardware.
+
+<table>
+  <thead>
+    <tr>
+      <th>Device</th>
+      <th>Supported</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>Audio codec</td><td>Yes</td><td>Supported on sun4i, sun5i, sun6i, sun8i-h2+, sun8i-h3</td></tr>
+    <tr><td>DMA</td><td>Yes</td><td></td></tr>
+    <tr><td>Fast Ethernet (sun4i/sun7i)</td><td>-</td><td></td></tr>
+    <tr><td>Framebuffer</td><td>Yes</td><td>Uses simplefb configured by bootloader</td></tr>
+    <tr><td>Gigabit Ethernet (sun6i/sun7i/sun9i)</td><td>Yes</td><td></td></tr>
+    <tr><td>Gigabit Ethernet (sun8i/sun50i)</td><td>Yes</td><td></td></tr>
+    <tr><td>GPIO</td><td>Yes</td><td></td></tr>
+    <tr><td>I2C</td><td>Yes</td><td></td></tr>
+    <tr><td>IR transceiver</td><td>-</td><td></td></tr>
+    <tr><td>P2WI/RSB</td><td>Yes</td><td></td></tr>
+    <tr><td>SD/MMC</td><td>Yes</td><td></td></tr>
+    <tr><td>SMP</td><td>Yes</td><td>Uses PSCI support in firmware</td></tr>
+    <tr><td>Thermal sensors</td><td>Yes</td><td>Supported on sun8i-a83t, sun8i-h3, sun50i-a64</td></tr>
+    <tr><td>Touch screen</td><td>Yes</td><td>Supported on sun5i</td></tr>
+    <tr><td>UART</td><td>Yes</td><td></td></tr>
+    <tr><td>USB 2.0</td><td>Yes</td><td></td></tr>
+    <tr><td>USB OTG</td><td>Experimental</td><td></td></tr>
+    <tr><td>Watchdog timer</td><td>Yes</td><td></td></tr>
+  </tbody>
+</table>
 
 # Installation
 

Add some pretty pictures
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:16:19 -0000	1.62
+++ wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:31:37 -0000	1.63
@@ -2,6 +2,9 @@
 
 NetBSD supports many boards based on Allwinner SoCs. Starting with NetBSD 8.0, FDT is used to configure devices. As a result, a large number of boards and configurations can be supported with a single kernel.
 
+<img src="https://pbs.twimg.com/media/DIRGmsOXcAEJu-j.jpg" width="300">
+<img src="https://pbs.twimg.com/media/DJYA7SCXUAEvEQk.jpg" width="300">
+
 [[!toc levels=2]]
 
 # Supported SoCs

wifi is not supported yet
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 23:20:38 -0000	1.51
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 23:26:29 -0000	1.52
@@ -135,7 +135,7 @@
 
 ## NetBSD 7 after July, 2017 and NetBSD 8
 
- - Raspberry Pi 3 (including wifi and SMP)
+ - Raspberry Pi 3 (excluding wifi and bluetooth)
 
 ## NetBSD current
 

Remove scary manual instructions for growing the root file system. This hasn't been needed for a long time now.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 23:14:07 -0000	1.50
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 23:20:38 -0000	1.51
@@ -32,51 +32,6 @@
 
       In minicom, run "minicom -s" and set hardware flow control to "no"
 
- - Growing the root file-system (**not required with NetBSD -current after 2015-04-07, or by NetBSD 7 after 2015-08-06**)
-   - During the partitioning process, do not delete or format the
-     first MSDOS (FAT) partition, as the Raspberry pi firmware is
-     hard coded to boot on the SDCAD / 1st MSDOS partition / Firmware
-     updates and boot loader.
-   - Copy /boot/cmdline.txt to /boot/cmdline.txt.orig
-   - Edit /boot/cmdline.txt and add the '-s' flag to the end of the first line of text to boot into single-user mode.
-   - For the next steps, the root filesystem mustn't be mounted rw. So reboot, and at the prompt to enter the pathname of shell,
-     press return for the default (/bin/sh).
-   - At the # prompt, type
-
-        "disklabel -i ld0" and press return.
-
-   - At the partition> prompt type "A" and press return.
-
-           Adjust disklabel sector from 4194304 to 62333952 [n]?
-           Type "y" and press return.
-
-   - partition> prompt type "a" and press return.
-
-           Filesystem type prompt, press return to use the current value (4.2BSD).
-           Start offset prompt, press return to use the current value.
-           Partition size prompt, type "$" and press return to grow the
-           partition to use all available free space.
-
-   - partition> prompt type "W" to save the changes to the disklabel.
-
-           Confirm this choice by typing "y" at the Label disk prompt.
-           Type "Q" and press return to quit disklabel.
-
-   - At the # prompt (shell), type
-
-           fsck -fy /dev/rld0a
-           resize_ffs -y /dev/rld0a
-
-   - This may take a few minutes, be patient!
-
-           fsck -fy /dev/rld0a
-           mount_msdos /dev/ld0e /boot
-           mv /boot/cmdline.txt.orig /boot/cmdline.txt
-           reboot
-
-    - When the system comes back up, the root file-system will have been expanded to
-	   fill the SD card.
-
 # Installation with sshramdisk image
  - You may use the  rpi_inst.img.gz file created by an evbarm build.
  - Connect Ethernet Cable to RPI.

port/evbarm: remove question now addressed in howto
--- wikisrc/ports/evbarm/raspberry_pi/comment_15_b0d4969dc7af58eb541ff8af225bc805._comment	2017-10-08 23:17:35.000000000 +0000
+++ /dev/null	2017-10-08 23:16:00.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="daniel.oelschlegel@aa334c96083f1def21cbf33cf3498e165b8b1d35"
- nickname="daniel.oelschlegel"
- subject="Raspberry 3 Support"
- date="2016-04-16T14:15:12Z"
- content="""
-What is the state of supporting of the newest hardware generation?
-"""]]

Add links to some sample Allwinner boards
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 14:39:23 -0000	1.61
+++ wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 23:16:19 -0000	1.62
@@ -12,25 +12,26 @@
       <th>Family</th>
       <th>SoC</th>
       <th>NetBSD version</th>
+      <th>Example boards</th>
       <th>Notes</th>
     </tr>
   </thead>
   <tbody>
-    <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td></td></tr>
+    <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware">Olimex A10-OLinuXino-LIME</a><td></td></tr>
     <tr><td>sun5i</td><td>A10s</td><td>-</td><td></td></tr>
     <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td></td></tr>
-    <tr><td>sun5i</td><td>GR8</td><td>8.99.2 and later</td><td></td></tr>
-    <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td></td></tr>
-    <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td></td></tr>
-    <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td></tr>
-    <tr><td>sun7i</td><td>A20</td><td>7.0 and later</td><td></td></tr>
+    <tr><td>sun5i</td><td>GR8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
+    <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chip">C.H.I.P.</a>, <a href="https://getchip.com/pages/pocketchip">Pocket C.H.I.P.</a></td><td></td></tr>
+    <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td><a href="http://linux-sunxi.org/Merrii_Hummingbird_A31">Merrii Hummingbird A31</a></td><td></td></tr>
+    <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td><td></td></tr>
+    <tr><td>sun7i</td><td>A20</td><td>7.0 and later</td><td><a href="https://linux-sunxi.org/Cubietech_Cubieboard2">Cubietech Cubieboard 2</a>, <a href="https://linux-sunxi.org/Cubietruck">Cubietech Cubietruck</a>, <a href="http://linux-sunxi.org/LeMaker_Banana_Pi">LeMaker Banana Pi</a></td><td></td></tr>
     <tr><td>sun8i</td><td>A23</td><td>-</td><td></td></tr>
     <tr><td>sun8i</td><td>A33</td><td>-</td><td></td></tr>
-    <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td></td></tr>
-    <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td></td></tr>
-    <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td></td></tr>
-    <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td></td></tr>
-    <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td>aarch32 mode</td></tr>
+    <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td><a href="http://www.banana-pi.org/m3.html">Sinovoip Banana Pi BPI-M3</a></td><td></td></tr>
+    <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td><a href="http://www.orangepi.org/orangepizero/">Xunlong Orange Pi Zero</a></td><td></td></tr>
+    <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>
+    <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
+    <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td>aarch32 mode</td></tr>
     <tr><td>sun50i</td><td>H5</td><td>-</td><td></td></tr>
     <tr><td>sun50i</td><td>H6</td><td>-</td><td></td></tr>
   </tbody>

ports/evbarm/raspberry_pi: clarify support
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 22:38:08 -0000	1.49
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 23:14:07 -0000	1.50
@@ -2,7 +2,7 @@
 
 This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
 
-Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.
+Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017.
 
 [[images/raspberrypi.jpg]]
 
@@ -160,7 +160,11 @@
 $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
 """]]
 
-# What works (NetBSD 7.0+)
+# What works
+
+## NetBSD 7 before July, 2017
+
+ - RaspberryPi 1, and 2 (including SMP)
  - multi-user boot with root on SD card
  - serial or graphics console (with EDID query / parsing)
  - DMA controller driver and sdhc(4) support
@@ -173,7 +177,15 @@
  - USB (host) - dwctwo(4)
  - USB Ethernet - usmsc(4)
  - X windows.
- - RaspberryPi 2 SMP
+
+## NetBSD 7 after July, 2017 and NetBSD 8
+
+ - Raspberry Pi 3 (including wifi and SMP)
+
+## NetBSD current
+
+ - Raspberry Pi 3 bluetooth
+ - Raspberry Pi 3 new SD host controller driver
 
 # What needs work
  - USB (host); isochronous transfers.

ports/evbarm/raspberry_pi: Change tense on NetBSD 7
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Apr 2017 14:48:31 -0000	1.48
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Oct 2017 22:38:08 -0000	1.49
@@ -11,7 +11,7 @@
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
 
 # Installation
- - The automatic nightly builds  on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/) provide image files that can be used for installation. The Raspberry Pi and Pi 2 ports will be part of the NetBSD 7 release.
+ - The automatic nightly builds  on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/) provide image files that can be used for installation. The Raspberry Pi and Pi 2 ports are part of the NetBSD 7 release.
     - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
     - The 'evbarm-earmv7hf/binary/gzimg/' directory, as of August 6th 2015, contains an armv7.img file that is optimized for Raspberry Pi 2.
     - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201412161700Z/evbarm-earmv6hf/binary/gzimg/)

ports/evbarm: include Pi3
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/ports/evbarm.mdwn	8 Oct 2017 14:42:05 -0000	1.39
+++ wikisrc/ports/evbarm.mdwn	8 Oct 2017 22:10:55 -0000	1.40
@@ -27,7 +27,7 @@
  - [[BeagleBone and BeagleBone Black|BeagleBone]]
  - [[NVIDIA Jetson TK1|Tegra]]
  - [[ODROID C1 and C1+|ODROID-C1]]
- - [[Raspberry Pi and Pi 2|Raspberry Pi]]
+ - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
 
 """
 
@@ -230,8 +230,8 @@
 Support for NVIDIA [[Tegra]] K1 SoCs is present in NetBSD-current and
 8.0_BETA. The Jetson TK1 board is currently supported.
 
-### Raspberry Pi Foundation **Raspberry Pi**/**Raspberry Pi 2**
-The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation. Both the Raspberry Pi and Raspberry Pi 2 are supported.
+### Raspberry Pi Foundation **Raspberry Pi**/**Raspberry Pi 2**/**Raspberry Pi 3**
+The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation.  The Raspberry Pi, Pi 2, and Pi 3 are supported.
 
 ### Rockchip PX2/RK3066/RK3188/RK3188+
 Various [[Rockchip]] family SoCs are supported by the ROCKCHIP kernel.

Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/ports/evbarm.mdwn	8 Oct 2017 14:40:47 -0000	1.38
+++ wikisrc/ports/evbarm.mdwn	8 Oct 2017 14:42:05 -0000	1.39
@@ -57,7 +57,7 @@
 systems should obtain an FPGA upgrade from ADI to revision 8 or later of the
 BECC.
 
-### Allwinner Technology A20/A31
+### Allwinner Technology
 Various boards based on [[Allwinner]] SoCs are supported, including the BananaPi, Cubieboard 2, Cubietruck, Cubieboard 4, and Merrii Hummingbird A31.
 
 ### Arcom **Viper**

Update title of Allwinner link
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- wikisrc/ports/evbarm.mdwn	6 Jun 2017 16:45:16 -0000	1.37
+++ wikisrc/ports/evbarm.mdwn	8 Oct 2017 14:40:47 -0000	1.38
@@ -23,8 +23,8 @@
 Matt Thomas is the maintainer of NetBSD/evbarm.
 
 ### Board specific information
+ - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone and BeagleBone Black|BeagleBone]]
- - [[Cubieboard 2, Cubietruck, Cubieboard 4, Banana Pi, and other Allwinner boards|Allwinner]]
  - [[NVIDIA Jetson TK1|Tegra]]
  - [[ODROID C1 and C1+|ODROID-C1]]
  - [[Raspberry Pi and Pi 2|Raspberry Pi]]

Add a table of supported SoCs, add simplified install guide, and xref the latest kernel config for an up-to-date list of supported hardware
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- wikisrc/ports/evbarm/allwinner.mdwn	11 Aug 2017 06:17:30 -0000	1.60
+++ wikisrc/ports/evbarm/allwinner.mdwn	8 Oct 2017 14:39:23 -0000	1.61
@@ -1,172 +1,48 @@
 [[!meta title="NetBSD/evbarm on Allwinner Technology SoCs"]]
 
-NetBSD 7.0 has support for A20 and A31 SoCs. NetBSD -current adds support for A80 SoCs.
+NetBSD supports many boards based on Allwinner SoCs. Starting with NetBSD 8.0, FDT is used to configure devices. As a result, a large number of boards and configurations can be supported with a single kernel.
 
 [[!toc levels=2]]
 
-# Supported boards
- - [Banana Pi](http://www.bananapi.org/p/product.html) (BPI)
- - Cubieboard 2 (CUBIEBOARD)
- - [Cubieboard 4](http://cubieboard.org/model/cb4/) (ALLWINNER_A80) *NetBSD-current*
- - Cubietruck (CUBIETRUCK)
- - [Merrii Hummingbird A31](http://www.merrii.com/en/pla_d.asp?id=172) (HUMMINGBIRD_A31)
+# Supported SoCs
+
+<table>
+  <thead>
+    <tr>
+      <th>Family</th>
+      <th>SoC</th>
+      <th>NetBSD version</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td></td></tr>
+    <tr><td>sun5i</td><td>A10s</td><td>-</td><td></td></tr>
+    <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td></td></tr>
+    <tr><td>sun5i</td><td>GR8</td><td>8.99.2 and later</td><td></td></tr>
+    <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td></td></tr>
+    <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td></td></tr>
+    <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td></tr>
+    <tr><td>sun7i</td><td>A20</td><td>7.0 and later</td><td></td></tr>
+    <tr><td>sun8i</td><td>A23</td><td>-</td><td></td></tr>
+    <tr><td>sun8i</td><td>A33</td><td>-</td><td></td></tr>
+    <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td></td></tr>
+    <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td></td></tr>
+    <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td></td></tr>
+    <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td></td></tr>
+    <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td>aarch32 mode</td></tr>
+    <tr><td>sun50i</td><td>H5</td><td>-</td><td></td></tr>
+    <tr><td>sun50i</td><td>H6</td><td>-</td><td></td></tr>
+  </tbody>
+</table>
+
 
 # Supported hardware
- - SoCs
-   - Cortex-A7: A20 (2-core), A31 (4-core), A80
-   - Cortex-A7/A15: A80 (4-core A7 + 4-core A15)
- - SD/MMC controller (DMA)
- - DMA controller
- - GPIO
-   - Configuration using FEX scripts is supported
- - UART
- - I2C
- - P2WI (A31) / RSB (A80)
- - PMU
-   - AXP209 (A20)
-   - AXP221 (A31)
-   - AXP806 (A80)
-   - AXP809 (A80)
- - Watchdog timer
- - RTC
-   - A20/A31: integrated RTC, PCF8563
-   - A80: AC100
- - Audio codec (A20/A31)
- - USB host
-   - OHCI
-   - EHCI
-   - OTG (A20)
- - SATA (A10/A20)
- - Gigabit Ethernet (GMAC)
- - HDMI
-   - DDC / EDID mode detection (A20/A31)
-   - Audio support (A20/A31)
- - Framebuffer (A20/A31/A80)
- - IR receiver (A20/A31/A80)
-
-# TODO
- - A10
-   - Interrupt controller
-   - EMAC
- - A31
-   - OTG
-   - IR transmitter
-   - 3G module
-   - TV input
- - A80
-   - MP
-   - big.LITTLE support
-   - USB3 (OTG and XHCI)
-   - IR transmitter
-   - HDMI (DDC and mode setting; currently relies on U-Boot for setup)
-   - Audio codec
- - All
-   - USB device mode
-   - SDIO (Bluetooth / WiFi)
-   - NAND
-   - VGA (Cubietruck, Hummingbird A31, Cubieboard4)
 
-# Installation
+Please refer to the [SUNXI kernel config](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/SUNXI) for a list of supported hardware.
 
-## A20 / A31 based boards
+# Installation
 
-* Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/armv7.img.gz* from
-NetBSD 7.0
-* Download a U-Boot build for your board
-  * Download the correct build from the linux-sunxi web site <http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi-mainline/u-boot-sunxi-mainline-20160902T174215-b615267/>.
-* Decompress the image via [[!template id=man name="gunzip" section="1"]]:
-[[!template  id=programlisting text="""
-# gunzip armv7.img.gz
-"""]]
-* Write the *u-boot-sunxi-with-spl.bin* loader to the empty space at the start of the base image:
-[[!template  id=programlisting text="""
-# dd if=u-boot-sunxi-with-spl.bin of=armv7.img bs=1k seek=8 conv=notrunc
-"""]]
-* Write the image to an SD card (e.g.: if the SD card is recognised as *sd0* -
-please check the [[!template id=man name="dmesg" section="8"]] output to be
-sure!):
-[[!template  id=programlisting text="""
-# dd if=armv7.img of=/dev/rsd0d bs=1m
-"""]]
-* Copy the kernel (*netbsd.ub*) for your board to the root of the MS-DOS
-partition on the SD card
-* Prepare a *boot.cmd* file for U-Boot boot loader containing the needed
-instructions regarding how to boot the kernel (basically the *bootargs* that are
-passed to the kernel and how to load the kernel from a device to the RAM and
-then boot it from the memory address):
-
-[[!template  id=filecontent name="boot.cmd" text="""
-setenv kernel_addr      82000000
-setenv kernel           netbsd.ub
-setenv bootargs         "root=ld0a"
-
-fatload mmc 0:1 ${kernel_addr} ${kernel}
-bootm ${kernel_addr}
-"""]]
-* The *boot.cmd* text file should be converted in a script image - *boot.scr*
-for U-Boot via [[!template id=man name="mkubootimage" section="1"]]:
-[[!template  id=programlisting text="""
-# mkubootimage -A arm -n armv7 -T script boot.cmd boot.scr
-"""]]
-* Copy the *boot.scr* to the MS-DOS partition of the SD card
-
-## A80 based boards
-
-* Cubieboard 4 U-Boot for SD card: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/allwinner/a80/cubieboard4-uboot.tgz>
-[[!template  id=programlisting text="""
-# dd if=u-boot-spl.bin of=/dev/sdd bs=1k seek=8
-# dd if=u-boot-sun9iw1p1.bin of=/dev/sdd bs=1k seek=19096
-"""]]
-* First partition needs to be at +20MB offset. Format it as MSDOS, copy 'netbsd.ub' to it as 'uImage'.
-
-# Big (endian) fun
-
-You can run this boards with a little endian (this is the default and implied by above install instructions)
-or with a big endian kernel and userland. However, kernel and userland endianness needs to match.
-
-To build a big endian release (or sets) use
-[[!template  id=programlisting text="""
-./build.sh -m evbearmv7hf-eb
-"""]]
-where -eb means endianness big, hf is hardware floating point support, and earm is the modern "extended" ABI for ARM CPUs, and finally v7 is version 7 of the supported instruction set.
-
-# FEX scripts
-
-Board configuration scripts can be found here: <https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config>. You can compile them with the "fex2bin" tool found here: <https://github.com/linux-sunxi/sunxi-tools>.
-
-To use, copy the compiled FEX to your MS-DOS partition, load it with U-Boot, and then tell the kernel where to find it with the "sysconfig=" boot option. For example, uEnv.txt on a Cubieboard2 might look like this:
-
-[[!template  id=filecontent name="uEnv.txt" text="""
-bootargs=root=ld0a sysconfig=0x43000000
-uenvcmd=mmc dev 0; mmc rescan; fatload mmc 0:1 43000000 cubieboard2.bin; fatload mmc 0:1 82000000 netbsd.ub; bootm 82000000
-"""]]
-
-Some pre-compiled .bin files can be found here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/allwinner/fex/>
-
-# Framebuffer console
-
-To use HDMI for the console device, add *console=fb* to bootargs in uEnv.txt.
-
-If the connected display does not let you disable overscan, you can add a margin to the framebuffer by with the *fb.margin* bootargs option. For example, to set a 25-pixel margin around the screen, add *fb.margin=25* to uEnv.txt
-
-# HDMI audio
-
-The default audio device is the analog audio codec. To change the default device, use the *audiocfg* command:
-
-[[!template  id=programlisting text="""

(Diff truncated)
fix boot.cfg syntax
Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 09:20:31 -0000	1.26
+++ wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 10:45:01 -0000	1.27
@@ -147,8 +147,8 @@
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
     cat > /mnt/boot.cfg
-    menu=Boot normally:dev hd0b;rndseed /entropy/entropy-file;boot netbsd
-    menu=Boot single user:dev hd0b;rndseed /entropy/entropy-file;boot netbsd -s
+    menu=Boot normally:dev hd0b:;rndseed /entropy/entropy-file;boot hd0b:netbsd
+    menu=Boot single user:dev hd0b:;rndseed /entropy/entropy-file;boot hd0b:netbsd -s
     menu=Drop to boot prompt:prompt
     default=1
     timeout=5
@@ -162,10 +162,10 @@
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
     cat > /mnt/boot.cfg
-    menu=Boot normally:dev hd0b;rndseed /entropy/entropy-file;boot netbsd
-    menu=Boot single user:dev hd0b;rndseed /entropy/entropy-file;boot netbsd -s
-    menu=Boot normally from hd1b:dev hd1b;rndseed /entropy/entropy-file;boot netbsd
-    menu=Boot single user from hd1b:dev hd1b;rndseed /entropy/entropy-file;boot netbsd -s
+    menu=Boot normally:dev hd0b:;rndseed /entropy/entropy-file;boot hd0b:netbsd
+    menu=Boot single user:dev hd0b:;rndseed /entropy/entropy-file;boot hd0b:netbsd -s
+    menu=Boot normally from hd1b::dev hd1b;rndseed /entropy/entropy-file;boot hd1b:netbsd
+    menu=Boot single user from hd1b::dev hd1b;rndseed /entropy/entropy-file;boot hd1b:netbsd -s
     menu=Drop to boot prompt:prompt
     default=1
     timeout=5

as suggested by pgoyette@
Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 07:07:48 -0000	1.25
+++ wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 09:20:31 -0000	1.26
@@ -24,7 +24,15 @@
 
 then raid the raids:
 
-check with dkctl wd0 listwedges and dkctl wd1 listwedges which dkN the raid wedges got, and insert them instead of dk4 and dk5 if yours differ:
+check with dkctl wd0 listwedges and dkctl wd1 listwedges which dk devices represent the raid gpt wedges; sample output:
+
+    /dev/rwd0: 4 wedges:
+    dk2: uefiboot1, 262144 blocks at 2048, type: msdos
+    dk4: raidsys1, 75497472 blocks at 264192, type: raidframe
+    dk6: raidswap1, 50331648 blocks at 75761664, type: raidframe
+    dk8: raidhome1, 1827431816 blocks at 126093312, type: raidframe
+
+and insert them instead of dk4 and dk5 if yours differ:
 
     cat > /tmp/raid0.conf
     START array

and another "nicer booting" iteration
Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 06:47:37 -0000	1.24
+++ wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 07:07:48 -0000	1.25
@@ -124,8 +124,6 @@
 
     mkdir /targetroot/entropy
 
-edit /targetroot/boot.cfg to use dev hd0b and hd1b respectively, and additionally to rndseed from /entropy/entropy-file instead of from /var (giving boot-hd0b.cfg abd boot-hd1b.cfg)
-
 create msdos filesystems on the uefiboot wedges:
 
     dkctl wd0 listwedges
@@ -140,15 +138,35 @@
     mount name=uefiboot1 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cp /targetroot/boot-hd0b.cfg /mnt/boot.cfg
+    cat > /mnt/boot.cfg
+    menu=Boot normally:dev hd0b;rndseed /entropy/entropy-file;boot netbsd
+    menu=Boot single user:dev hd0b;rndseed /entropy/entropy-file;boot netbsd -s
+    menu=Drop to boot prompt:prompt
+    default=1
+    timeout=5
+    clear=1
+    ^D
     umount /mnt
 
+usually the system will boot from wd0 aka hd0, but if that disk has a problem, depending on how dead it is you may want to boot from wd1-as-hd0 or wd1-as-hd1:
+
     mount name=uefiboot2 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cp /targetroot/boot-hd1b.cfg /mnt/boot.cfg
+    cat > /mnt/boot.cfg
+    menu=Boot normally:dev hd0b;rndseed /entropy/entropy-file;boot netbsd
+    menu=Boot single user:dev hd0b;rndseed /entropy/entropy-file;boot netbsd -s
+    menu=Boot normally from hd1b:dev hd1b;rndseed /entropy/entropy-file;boot netbsd
+    menu=Boot single user from hd1b:dev hd1b;rndseed /entropy/entropy-file;boot netbsd -s
+    menu=Drop to boot prompt:prompt
+    default=1
+    timeout=5
+    clear=1
+    ^D
     umount /mnt
 
+If the system is going to be in an inconvenient location (so walking up to it with a memstick becomes a project), consider also putting an install kernel on uefiboot* as rescue++.
+
 ### configure the system (manually, colorful curses elided. sysinst Needs Work.)
 
     chroot /targetroot su -

add disapprove
Index: wikisrc/users/spz/projects.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/projects.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/spz/projects.mdwn	26 Sep 2017 08:10:49 -0000	1.2
+++ wikisrc/users/spz/projects.mdwn	4 Oct 2017 06:50:51 -0000	1.3
@@ -10,6 +10,8 @@
 
 - get refa and virini set up on shadow
 
+- disapprove script (take spam in my mailing list owner inbox, feed it to spamassassin)
+
 - [[releng-pkgsrc pullups|https://releng.netbsd.org/cgi-bin/req-pkgsrc.cgi]]
 
 - research [[signing TNF generated packages|pkgsig]]

make a clearer boot.cfg description and also mention rndseed
Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 06:15:50 -0000	1.23
+++ wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 06:47:37 -0000	1.24
@@ -122,7 +122,9 @@
 
 ### bootability
 
-edit /targetroot/boot.cfg to boot hd0b:netbsd instead of plain netbsd
+    mkdir /targetroot/entropy
+
+edit /targetroot/boot.cfg to use dev hd0b and hd1b respectively, and additionally to rndseed from /entropy/entropy-file instead of from /var (giving boot-hd0b.cfg abd boot-hd1b.cfg)
 
 create msdos filesystems on the uefiboot wedges:
 
@@ -138,13 +140,13 @@
     mount name=uefiboot1 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cp /targetroot/boot.cfg /mnt
+    cp /targetroot/boot-hd0b.cfg /mnt/boot.cfg
     umount /mnt
 
     mount name=uefiboot2 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cp /targetroot/boot.cfg /mnt
+    cp /targetroot/boot-hd1b.cfg /mnt/boot.cfg
     umount /mnt
 
 ### configure the system (manually, colorful curses elided. sysinst Needs Work.)

it can 'see' the next partition but it doesn't use it automagically
Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 15:25:55 -0000	1.22
+++ wikisrc/users/spz/moderndisk.mdwn	4 Oct 2017 06:15:50 -0000	1.23
@@ -122,6 +122,8 @@
 
 ### bootability
 
+edit /targetroot/boot.cfg to boot hd0b:netbsd instead of plain netbsd
+
 create msdos filesystems on the uefiboot wedges:
 
     dkctl wd0 listwedges
@@ -131,16 +133,18 @@
      -> my uefiboot2 is dk3
     newfs_msdos -F 32 -b 1024 /dev/rdk3
 
-copy the uefi boot things and the kernel to both:
+copy the uefi boot things to both:
 
     mount name=uefiboot1 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
+    cp /targetroot/boot.cfg /mnt
     umount /mnt
 
     mount name=uefiboot2 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
+    cp /targetroot/boot.cfg /mnt
     umount /mnt
 
 ### configure the system (manually, colorful curses elided. sysinst Needs Work.)

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 15:06:15 -0000	1.21
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 15:25:55 -0000	1.22
@@ -11,7 +11,7 @@
     gpt add -l uefiboot1 -a 1024k -s 128M -t efi wd0
     gpt add -l uefiboot2 -a 1024k -s 128M -t efi wd1
 
-if your disks should have 4k native sectors, use -s 256M.
+if your disks have 4k native sectors, use -s 256M.
 
 while I'm here, also make the raid wedges and raided swap space. I have 1TB disks, and want enough swap to be able to dump my entire RAM if necessary:
 
@@ -82,7 +82,7 @@
 since uefi needs the rootfs 64 blocks after the end of the uefi partition, and the raidframe label already uses those up.
 
     disklabel -e raid0
-     -> 2 partitions, a and e, 26G and 10G respectively
+     -> 2 partitions, a and e, 26G and 10G respectively, a starting at 0
 
     newfs -O2 /dev/raid0a
     newfs -O2 /dev/raid0e
@@ -107,9 +107,9 @@
 
 ### put an OS on
 
-    mount name=root /targetroot
+    mount /dev/raid0a /targetroot
     mkdir /targetroot/var /targetroot/home
-    mount name=var /targetroot/var
+    mount /dev/raid0e /targetroot/var
     mount name=home /targetroot/home
     cd /targetroot
 
@@ -174,6 +174,4 @@
 
 add users, edit security.conf and daily.conf
 
-reboot
-
-Issues: loading entropy won't work in this setup
+reboot from disk

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:36:33 -0000	1.20
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 15:06:15 -0000	1.21
@@ -15,10 +15,12 @@
 
 while I'm here, also make the raid wedges and raided swap space. I have 1TB disks, and want enough swap to be able to dump my entire RAM if necessary:
 
-    gpt add -l raidwedge1 -a 4k -s 1860000000 -t raid wd0
-    gpt add -l raidwedge2 -a 4k -s 1860000000 -t raid wd1
-    gpt add -l raidswap1  -a 4k -s 93260000   -t raid wd0
-    gpt add -l raidswap2  -a 4k -s 93260000   -t raid wd1
+    gpt add -l raidsys1   -a 4k -s 36G  -t raid wd0
+    gpt add -l raidsys2   -a 4k -s 36G  -t raid wd1
+    gpt add -l raidswap1  -a 4k -s 24G  -t raid wd0
+    gpt add -l raidswap2  -a 4k -s 24G  -t raid wd1
+    gpt add -l raidhome1  -a 4k -s 870G -t raid wd0
+    gpt add -l raidhome2  -a 4k -s 870G -t raid wd0
 
 then raid the raids:
 
@@ -73,27 +75,35 @@
     raidctl -i raid1
     raidctl -A yes raid1
 
+the home raid (raid2) gets built the same as the swap raid, apart from taking a long time in the raid -i stage.
 
-### wedges on the raid
+### system raid: with disklabel
 
-    gpt create raid0
+since uefi needs the rootfs 64 blocks after the end of the uefi partition, and the raidframe label already uses those up.
+
+    disklabel -e raid0
+     -> 2 partitions, a and e, 26G and 10G respectively
+
+    newfs -O2 /dev/raid0a
+    newfs -O2 /dev/raid0e
+
+### swap raid
+
+    gpt create raid1
+    gpt add -a 4k -t swap -l swap raid1
+
+### home raid
+
+    gpt create raid2
 
 align to 4k for somewhat better performance
 
-    gpt add -a 4k -s 26G -l root raid0
-    gpt add -a 4k -s 10G -l var  raid0
-    gpt add -a 4k -s 1784502296 -l home raid0
+    gpt add -a 4k -l home raid2
 
 and newfs:
 
-    newfs -O2 name=root
-    newfs -O2 name=var
     newfs -O2 name=home
 
-### swapraid
-
-    gpt create raid1
-    gpt add -a 4k -t swap -l swap raid1
 
 ### put an OS on
 
@@ -126,15 +136,11 @@
     mount name=uefiboot1 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cp /targetroot/netbsd /mnt
-    cp /targetroot/boot.cfg /mnt
     umount /mnt
 
     mount name=uefiboot2 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cp /targetroot/netbsd /mnt
-    cp /targetroot/boot.cfg /mnt
     umount /mnt
 
 ### configure the system (manually, colorful curses elided. sysinst Needs Work.)
@@ -145,10 +151,10 @@
 
     cd /etc
     cat > fstab
-    NAME=root /      ffs  rw 1 1
-    NAME=var  /var   ffs  rw 1 2
-    NAME=home /home  ffs  rw 1 3
-    NAME=swap none   swap sw 0 0
+    /dev/raid0a     /               ffs     rw 1 1
+    /dev/raid0e     /var            ffs     rw 1 2
+    NAME=home       /home           ffs     rw 1 3
+    NAME=swap       none            swap    sw 0 0
     kernfs          /kern           kernfs  rw
     ptyfs           /dev/pts        ptyfs   rw
     procfs          /proc           procfs  rw

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:32:57 -0000	1.19
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:36:33 -0000	1.20
@@ -155,6 +155,8 @@
     tmpfs           /tmp            tmpfs   rw,-s128m
     ^D
 
+    mkdir /kern /proc
+
     vi rc.conf
      -> hostname, dhcpcd, wscons, sshd, random_file=/entropy/entropy-file, ...
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:24:52 -0000	1.18
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:32:57 -0000	1.19
@@ -95,6 +95,21 @@
     gpt create raid1
     gpt add -a 4k -t swap -l swap raid1
 
+### put an OS on
+
+    mount name=root /targetroot
+    mkdir /targetroot/var /targetroot/home
+    mount name=var /targetroot/var
+    mount name=home /targetroot/home
+    cd /targetroot
+
+    for i in base comp etc games kern-GENERIC man misc modules tests text; do
+        tar xzpf /amd64/binary/sets/$i.tgz
+    done
+
+    cd dev
+    ./MAKEDEV all
+
 ### bootability
 
 create msdos filesystems on the uefiboot wedges:
@@ -111,30 +126,17 @@
     mount name=uefiboot1 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cd /mnt ; tar xzpf /amd64/binary/sets/kern-GENERIC.tgz ; cd /
+    cp /targetroot/netbsd /mnt
+    cp /targetroot/boot.cfg /mnt
     umount /mnt
 
     mount name=uefiboot2 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
-    cd /mnt ; tar xzpf /amd64/binary/sets/kern-GENERIC.tgz ; cd /
+    cp /targetroot/netbsd /mnt
+    cp /targetroot/boot.cfg /mnt
     umount /mnt
 
-### put an OS on
-
-    mount name=root /targetroot
-    mkdir /targetroot/var /targetroot/home
-    mount name=var /targetroot/var
-    mount name=home /targetroot/home
-    cd /targetroot
-
-    for i in base comp etc games kern-GENERIC man misc modules tests text; do
-        tar xzpf /amd64/binary/sets/$i.tgz
-    done
-
-    cd dev
-    ./MAKEDEV all
-
 ### configure the system (manually, colorful curses elided. sysinst Needs Work.)
 
     chroot /targetroot su -
@@ -153,8 +155,6 @@
     tmpfs           /tmp            tmpfs   rw,-s128m
     ^D
 
-boot.cfg wants to load entropy from /var and that's not mounted yet; mkdir /entropy and edit boot.cfg to load entropy from there.
-
     vi rc.conf
      -> hostname, dhcpcd, wscons, sshd, random_file=/entropy/entropy-file, ...
 
@@ -167,3 +167,5 @@
 add users, edit security.conf and daily.conf
 
 reboot
+
+Issues: loading entropy won't work in this setup

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:18:21 -0000	1.17
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:24:52 -0000	1.18
@@ -93,7 +93,7 @@
 ### swapraid
 
     gpt create raid1
-    gpt add -a 4k -l swap raid1
+    gpt add -a 4k -t swap -l swap raid1
 
 ### bootability
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:14:29 -0000	1.16
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:18:21 -0000	1.17
@@ -162,6 +162,8 @@
 
     rm localtime && ln -s /usr/share/zoneinfo/<yourzone> localtime
 
-add users, edit security.conf and daily.conf
+edit wscons.conf for the encoding of your keyboard if not US
 
+add users, edit security.conf and daily.conf
 
+reboot

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:10:40 -0000	1.15
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:14:29 -0000	1.16
@@ -106,16 +106,18 @@
      -> my uefiboot2 is dk3
     newfs_msdos -F 32 -b 1024 /dev/rdk3
 
-copy the uefi boot things to both:
+copy the uefi boot things and the kernel to both:
 
     mount name=uefiboot1 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
+    cd /mnt ; tar xzpf /amd64/binary/sets/kern-GENERIC.tgz ; cd /
     umount /mnt
 
     mount name=uefiboot2 /mnt
     mkdir -p /mnt/EFI/boot
     cp /usr/mdec/*.efi /mnt/EFI/boot
+    cd /mnt ; tar xzpf /amd64/binary/sets/kern-GENERIC.tgz ; cd /
     umount /mnt
 
 ### put an OS on

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 10:48:04 -0000	1.14
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 11:10:40 -0000	1.15
@@ -78,12 +78,9 @@
 
     gpt create raid0
 
-root needs a magic starting block
-
-    gpt add -b 64 -s 26G -l root raid0
-
-rest just want to be aligned for better performance
+align to 4k for somewhat better performance
 
+    gpt add -a 4k -s 26G -l root raid0
     gpt add -a 4k -s 10G -l var  raid0
     gpt add -a 4k -s 1784502296 -l home raid0
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:51:37 -0000	1.13
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 10:48:04 -0000	1.14
@@ -85,7 +85,7 @@
 rest just want to be aligned for better performance
 
     gpt add -a 4k -s 10G -l var  raid0
-    gpt add -a 4k        -l home raid0
+    gpt add -a 4k -s 1784502296 -l home raid0
 
 and newfs:
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:50:01 -0000	1.12
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:51:37 -0000	1.13
@@ -82,7 +82,7 @@
 
     gpt add -b 64 -s 26G -l root raid0
 
-rest just need to be aligned
+rest just want to be aligned for better performance
 
     gpt add -a 4k -s 10G -l var  raid0
     gpt add -a 4k        -l home raid0

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:11:48 -0000	1.11
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:50:01 -0000	1.12
@@ -77,7 +77,13 @@
 ### wedges on the raid
 
     gpt create raid0
-    gpt add -a 4k -s 26G -l root raid0
+
+root needs a magic starting block
+
+    gpt add -b 64 -s 26G -l root raid0
+
+rest just need to be aligned
+
     gpt add -a 4k -s 10G -l var  raid0
     gpt add -a 4k        -l home raid0
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:09:14 -0000	1.10
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:11:48 -0000	1.11
@@ -15,10 +15,10 @@
 
 while I'm here, also make the raid wedges and raided swap space. I have 1TB disks, and want enough swap to be able to dump my entire RAM if necessary:
 
-    gpt add -l raidwedge1 -a 8 -s 1860000000 -t raid wd0
-    gpt add -l raidwedge2 -a 8 -s 1860000000 -t raid wd1
-    gpt add -l raidswap1  -a 8 -s 93260000   -t raid wd0
-    gpt add -l raidswap2  -a 8 -s 93260000   -t raid wd1
+    gpt add -l raidwedge1 -a 4k -s 1860000000 -t raid wd0
+    gpt add -l raidwedge2 -a 4k -s 1860000000 -t raid wd1
+    gpt add -l raidswap1  -a 4k -s 93260000   -t raid wd0
+    gpt add -l raidswap2  -a 4k -s 93260000   -t raid wd1
 
 then raid the raids:
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:59:05 -0000	1.9
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 08:09:14 -0000	1.10
@@ -71,6 +71,7 @@
     raidctl -C /tmp/raid1.conf raid1
     raidctl -I `date +%Y%m%d01` raid1
     raidctl -i raid1
+    raidctl -A yes raid1
 
 
 ### wedges on the raid

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:58:44 -0000	1.8
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:59:05 -0000	1.9
@@ -47,7 +47,7 @@
 
 raid0 is supposed to have the root on it:
 
-    raidctl -A root raid0
+    raidctl -A softroot raid0
 
 and the swap raid:
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:49:35 -0000	1.7
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:58:44 -0000	1.8
@@ -42,7 +42,8 @@
 and apply:
 
     raidctl -C /tmp/raid0.conf raid0
-    raidctl -I `date +%Y%m%d00`
+    raidctl -I `date +%Y%m%d00` raid0
+    raidctl -i raid0
 
 raid0 is supposed to have the root on it:
 
@@ -68,7 +69,9 @@
 and apply:
 
     raidctl -C /tmp/raid1.conf raid1
-    raidctl -I `date +%Y%m%d01`
+    raidctl -I `date +%Y%m%d01` raid1
+    raidctl -i raid1
+
 
 ### wedges on the raid
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:30:55 -0000	1.6
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:49:35 -0000	1.7
@@ -13,12 +13,12 @@
 
 if your disks should have 4k native sectors, use -s 256M.
 
-while I'm here, also make the raid wedges and raided swap space:
+while I'm here, also make the raid wedges and raided swap space. I have 1TB disks, and want enough swap to be able to dump my entire RAM if necessary:
 
     gpt add -l raidwedge1 -a 8 -s 1860000000 -t raid wd0
-    gpt add -l raidwedge2 -a 8 -s 1860000000 -t raid wd2
+    gpt add -l raidwedge2 -a 8 -s 1860000000 -t raid wd1
     gpt add -l raidswap1  -a 8 -s 93260000   -t raid wd0
-    gpt add -l raidswap2  -a 8 -s 93260000   -t raid wd2
+    gpt add -l raidswap2  -a 8 -s 93260000   -t raid wd1
 
 then raid the raids:
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:29:06 -0000	1.5
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:30:55 -0000	1.6
@@ -126,7 +126,7 @@
     cd dev
     ./MAKEDEV all
 
-### configure the system (manually, colorful curses elided)
+### configure the system (manually, colorful curses elided. sysinst Needs Work.)
 
     chroot /targetroot su -
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:10:20 -0000	1.4
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:29:06 -0000	1.5
@@ -2,6 +2,8 @@
 
 I have a new machine that wants to boot UEFI, and it has two disks that I want to mirror. I have booted NetBSD-8.0_BETA-amd64-uefi-install.img off a USB stick, and went from sysinst to shell. This implies I have tools and sets (in /amd64/binary/sets) locally, and a /targetroot directory.
 
+Several config files need to be created; I show them as "cat &gt; file" because that shows what goes in there but by all means use a proper editor if you can't use cut+paste.
+
 UEFI does not use installboot, but instead you create a UEFI boot partition which is msdos:
 
     gpt create wd0
@@ -141,9 +143,11 @@
     procfs          /proc           procfs  rw
     tmpfs           /tmp            tmpfs   rw,-s128m
     ^D
-   
+
+boot.cfg wants to load entropy from /var and that's not mounted yet; mkdir /entropy and edit boot.cfg to load entropy from there.
+
     vi rc.conf
-     -> hostname, dhcpcd, wscons, sshd, ...
+     -> hostname, dhcpcd, wscons, sshd, random_file=/entropy/entropy-file, ...
 
 fix up timezone if necessary:
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:08:46 -0000	1.3
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:10:20 -0000	1.4
@@ -111,43 +111,43 @@
 
 ### put an OS on
 
-   mount name=root /targetroot
-   mkdir /targetroot/var /targetroot/home
-   mount name=var /targetroot/var
-   mount name=home /targetroot/home
-   cd /targetroot
-
-   for i in base comp etc games kern-GENERIC man misc modules tests text; do
-       tar xzpf /amd64/binary/sets/$i.tgz
-   done
+    mount name=root /targetroot
+    mkdir /targetroot/var /targetroot/home
+    mount name=var /targetroot/var
+    mount name=home /targetroot/home
+    cd /targetroot
+
+    for i in base comp etc games kern-GENERIC man misc modules tests text; do
+        tar xzpf /amd64/binary/sets/$i.tgz
+    done
 
-   cd dev
-   ./MAKEDEV all
+    cd dev
+    ./MAKEDEV all
 
 ### configure the system (manually, colorful curses elided)
 
-   chroot /targetroot su -
+    chroot /targetroot su -
 
-   passwd root
+    passwd root
 
-   cd /etc
-   cat > fstab
-   NAME=root /      ffs  rw 1 1
-   NAME=var  /var   ffs  rw 1 2
-   NAME=home /home  ffs  rw 1 3
-   NAME=swap none   swap sw 0 0
-   kernfs          /kern           kernfs  rw
-   ptyfs           /dev/pts        ptyfs   rw
-   procfs          /proc           procfs  rw
-   tmpfs           /tmp            tmpfs   rw,-s128m
-   ^D
+    cd /etc
+    cat > fstab
+    NAME=root /      ffs  rw 1 1
+    NAME=var  /var   ffs  rw 1 2
+    NAME=home /home  ffs  rw 1 3
+    NAME=swap none   swap sw 0 0
+    kernfs          /kern           kernfs  rw
+    ptyfs           /dev/pts        ptyfs   rw
+    procfs          /proc           procfs  rw
+    tmpfs           /tmp            tmpfs   rw,-s128m
+    ^D
    
-   vi rc.conf
+    vi rc.conf
      -> hostname, dhcpcd, wscons, sshd, ...
 
 fix up timezone if necessary:
 
-   rm localtime && ln -s /usr/share/zoneinfo/<yourzone> localtime
+    rm localtime && ln -s /usr/share/zoneinfo/<yourzone> localtime
 
 add users, edit security.conf and daily.conf
 

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 06:35:40 -0000	1.2
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 07:08:46 -0000	1.3
@@ -1,6 +1,6 @@
 ## UEFI-Boot, GPT and raidframe
 
-I have a new machine that wants to boot UEFI, and it has two disks that I want to mirror. I have booted NetBSD-8.0_BETA-amd64-uefi-install.img off a USB stick, and went from sysinst to shell. This implies I have tools and sets locally, and a /targetroot directory.
+I have a new machine that wants to boot UEFI, and it has two disks that I want to mirror. I have booted NetBSD-8.0_BETA-amd64-uefi-install.img off a USB stick, and went from sysinst to shell. This implies I have tools and sets (in /amd64/binary/sets) locally, and a /targetroot directory.
 
 UEFI does not use installboot, but instead you create a UEFI boot partition which is msdos:
 
@@ -81,6 +81,11 @@
     newfs -O2 name=var
     newfs -O2 name=home
 
+### swapraid
+
+    gpt create raid1
+    gpt add -a 4k -l swap raid1
+
 ### bootability
 
 create msdos filesystems on the uefiboot wedges:
@@ -104,3 +109,46 @@
     cp /usr/mdec/*.efi /mnt/EFI/boot
     umount /mnt
 
+### put an OS on
+
+   mount name=root /targetroot
+   mkdir /targetroot/var /targetroot/home
+   mount name=var /targetroot/var
+   mount name=home /targetroot/home
+   cd /targetroot
+
+   for i in base comp etc games kern-GENERIC man misc modules tests text; do
+       tar xzpf /amd64/binary/sets/$i.tgz
+   done
+
+   cd dev
+   ./MAKEDEV all
+
+### configure the system (manually, colorful curses elided)
+
+   chroot /targetroot su -
+
+   passwd root
+
+   cd /etc
+   cat > fstab
+   NAME=root /      ffs  rw 1 1
+   NAME=var  /var   ffs  rw 1 2
+   NAME=home /home  ffs  rw 1 3
+   NAME=swap none   swap sw 0 0
+   kernfs          /kern           kernfs  rw
+   ptyfs           /dev/pts        ptyfs   rw
+   procfs          /proc           procfs  rw
+   tmpfs           /tmp            tmpfs   rw,-s128m
+   ^D
+   
+   vi rc.conf
+     -> hostname, dhcpcd, wscons, sshd, ...
+
+fix up timezone if necessary:
+
+   rm localtime && ln -s /usr/share/zoneinfo/<yourzone> localtime
+
+add users, edit security.conf and daily.conf
+
+

Index: wikisrc/users/spz/moderndisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/moderndisk.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 06:07:35 -0000	1.1
+++ wikisrc/users/spz/moderndisk.mdwn	3 Oct 2017 06:35:40 -0000	1.2
@@ -1,6 +1,6 @@
 ## UEFI-Boot, GPT and raidframe
 
-I have a new machine that wants to boot UEFI, and it has two disks that I want to mirror.
+I have a new machine that wants to boot UEFI, and it has two disks that I want to mirror. I have booted NetBSD-8.0_BETA-amd64-uefi-install.img off a USB stick, and went from sysinst to shell. This implies I have tools and sets locally, and a /targetroot directory.
 
 UEFI does not use installboot, but instead you create a UEFI boot partition which is msdos:
 
@@ -68,4 +68,39 @@
     raidctl -C /tmp/raid1.conf raid1
     raidctl -I `date +%Y%m%d01`
 
+### wedges on the raid
+
+    gpt create raid0
+    gpt add -a 4k -s 26G -l root raid0
+    gpt add -a 4k -s 10G -l var  raid0
+    gpt add -a 4k        -l home raid0
+
+and newfs:
+
+    newfs -O2 name=root
+    newfs -O2 name=var
+    newfs -O2 name=home
+
+### bootability
+
+create msdos filesystems on the uefiboot wedges:
+
+    dkctl wd0 listwedges
+     -> my uefiboot1 is dk2
+    newfs_msdos -F 32 -b 1024 /dev/rdk2
+    dkctl wd1 listwedges
+     -> my uefiboot2 is dk3
+    newfs_msdos -F 32 -b 1024 /dev/rdk3
+
+copy the uefi boot things to both:
+
+    mount name=uefiboot1 /mnt
+    mkdir -p /mnt/EFI/boot
+    cp /usr/mdec/*.efi /mnt/EFI/boot
+    umount /mnt
+
+    mount name=uefiboot2 /mnt
+    mkdir -p /mnt/EFI/boot
+    cp /usr/mdec/*.efi /mnt/EFI/boot
+    umount /mnt
 

--- /dev/null	2017-10-03 06:00:34.000000000 +0000
+++ wikisrc/users/spz/moderndisk.mdwn	2017-10-03 06:07:50.000000000 +0000
@@ -0,0 +1,71 @@
+## UEFI-Boot, GPT and raidframe
+
+I have a new machine that wants to boot UEFI, and it has two disks that I want to mirror.
+
+UEFI does not use installboot, but instead you create a UEFI boot partition which is msdos:
+
+    gpt create wd0
+    gpt create wd1
+    gpt add -l uefiboot1 -a 1024k -s 128M -t efi wd0
+    gpt add -l uefiboot2 -a 1024k -s 128M -t efi wd1
+
+if your disks should have 4k native sectors, use -s 256M.
+
+while I'm here, also make the raid wedges and raided swap space:
+
+    gpt add -l raidwedge1 -a 8 -s 1860000000 -t raid wd0
+    gpt add -l raidwedge2 -a 8 -s 1860000000 -t raid wd2
+    gpt add -l raidswap1  -a 8 -s 93260000   -t raid wd0
+    gpt add -l raidswap2  -a 8 -s 93260000   -t raid wd2
+
+then raid the raids:
+
+check with dkctl wd0 listwedges and dkctl wd1 listwedges which dkN the raid wedges got, and insert them instead of dk4 and dk5 if yours differ:
+
+    cat > /tmp/raid0.conf
+    START array
+    1 2 0
+
+    START disks
+    /dev/dk4
+    /dev/dk5
+
+    START layout
+    128 1 1 1
+
+    START queue
+    fifo 100
+    ^D
+
+and apply:
+
+    raidctl -C /tmp/raid0.conf raid0
+    raidctl -I `date +%Y%m%d00`
+
+raid0 is supposed to have the root on it:
+
+    raidctl -A root raid0
+
+and the swap raid:
+
+    cat > /tmp/raid1.conf
+    START array
+    1 2 0
+
+    START disks
+    /dev/dk6
+    /dev/dk7
+
+    START layout
+    128 1 1 1
+
+    START queue
+    fifo 100
+    ^D
+
+and apply:
+
+    raidctl -C /tmp/raid1.conf raid1
+    raidctl -I `date +%Y%m%d01`
+
+

Add a comment
Contact | Disclaimer | Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
NetBSD® is a registered trademark of The NetBSD Foundation, Inc.