Recent changes to this wiki:

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/releng/netbsd9.mdwn	9 Dec 2018 23:20:22 -0000	1.29
+++ wikisrc/releng/netbsd9.mdwn	11 Dec 2018 20:20:33 -0000	1.30
@@ -36,9 +36,8 @@
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and possibly alpha, aarch64
    - [[!template id=pr number=53124]] (FFS is slow because pmap_update doesn't scale)
-   - on alpha triggers machine check - verify on other machine?
-     [[https://mail-index.netbsd.org/source-changes-d/2018/05/22/msg010188.html]]
-   - aarch64 completely untested
+   - all known issues fixed - confirmed working on amd64 and alpha
+   - patch for aarch64 being tested
 * XEN AVX working
    - ~~[[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set~~ (done)
 * ZFS

markdown
Index: wikisrc/projects/project/npf_improvements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/npf_improvements.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/npf_improvements.mdwn	10 Dec 2018 14:33:09 -0000	1.2
+++ wikisrc/projects/project/npf_improvements.mdwn	10 Dec 2018 14:34:05 -0000	1.3
@@ -13,6 +13,7 @@
 
 description="""
 Improvements that can be done to NPF with reference to WIP code/descriptions:
+
 - Import [thmap](https://github.com/rmind/thmap), needed for [newer NPF](https://github.com/rmind/npf/)
 - [WIP dynamic NAT address and NETMAP](https://github.com/rmind/npf/pull/9)
 - Use of "any"  

Markdown
Index: wikisrc/projects/project/npf_improvements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/npf_improvements.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/npf_improvements.mdwn	10 Dec 2018 14:31:53 -0000	1.1
+++ wikisrc/projects/project/npf_improvements.mdwn	10 Dec 2018 14:33:09 -0000	1.2
@@ -3,8 +3,8 @@
 title="NPF improvements"
 
 contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
-[tech-net](mailto:tech-net@NetBSD.org)
+[tech-kern](mailto:tech-kern@NetBSD.org)  
+[tech-net](mailto:tech-net@NetBSD.org)  
 [rmind](mailto:rmind@NetBSD.org)
 """
 
@@ -13,15 +13,11 @@
 
 description="""
 Improvements that can be done to NPF with reference to WIP code/descriptions:
-
 - Import [thmap](https://github.com/rmind/thmap), needed for [newer NPF](https://github.com/rmind/npf/)
-
 - [WIP dynamic NAT address and NETMAP](https://github.com/rmind/npf/pull/9)
-
-- Use of "any"
-  ```map $ext_if dynamic any -> $ext_v4 pass family inet4 from $int_net```
+- Use of "any"  
+  ```map $ext_if dynamic any -> $ext_v4 pass family inet4 from $int_net```.  
   needs a few syntactic fixes/wrappers (e.g. loading can just handle "any" here, since it's actually correct, just merely not supported by the syntax; you can replace it with 0.0.0.0, though)
-
 - traffic redirection, [1](http://www.netbsd.org/~rmind/npf_ext_route.c) [2](http://www.netbsd.org/~rmind/npfext_route.c)
   I think it just needs IPv6 handling and testing
 """

Attempt to summarize IRC conversation with links that can be referenced
as a project.
--- /dev/null	2018-12-10 14:32:06.000000000 +0000
+++ wikisrc/projects/project/npf_improvements.mdwn	2018-12-10 14:32:12.000000000 +0000
@@ -0,0 +1,28 @@
+[[!template id=project
+
+title="NPF improvements"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+[tech-net](mailto:tech-net@NetBSD.org)
+[rmind](mailto:rmind@NetBSD.org)
+"""
+
+category="networking"
+difficulty="medium"
+
+description="""
+Improvements that can be done to NPF with reference to WIP code/descriptions:
+
+- Import [thmap](https://github.com/rmind/thmap), needed for [newer NPF](https://github.com/rmind/npf/)
+
+- [WIP dynamic NAT address and NETMAP](https://github.com/rmind/npf/pull/9)
+
+- Use of "any"
+  ```map $ext_if dynamic any -> $ext_v4 pass family inet4 from $int_net```
+  needs a few syntactic fixes/wrappers (e.g. loading can just handle "any" here, since it's actually correct, just merely not supported by the syntax; you can replace it with 0.0.0.0, though)
+
+- traffic redirection, [1](http://www.netbsd.org/~rmind/npf_ext_route.c) [2](http://www.netbsd.org/~rmind/npfext_route.c)
+  I think it just needs IPv6 handling and testing
+"""
+]]

Add starting point of release notes. Mark some stuff as done.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/releng/netbsd9.mdwn	7 Dec 2018 22:44:15 -0000	1.28
+++ wikisrc/releng/netbsd9.mdwn	9 Dec 2018 23:20:22 -0000	1.29
@@ -46,18 +46,18 @@
 * ~~~kASan for aarch64~~~ (done)
 * compiler-rt in the base with enabled features for Clang/LLVM
 * LVM mirror target
-* add NVMM
+* ~~~add NVMM~~~ (done)
 * ~~~plug kernel pointer leaks~~~ (done)
 * fix Nouveau, some GPUs stopped working after the update
 
 ## Nice to have
 
 * gcc 8+ from a sanitizers point of view
-* ~~~arm: GENERIC kernel config for armv7 boards.~~~
-* ~~~arm64: Support for servers following SBSA/SBBR standards~~~
+* ~~~arm: GENERIC kernel config for armv7 boards.~~~ (done)
+* ~~~arm64: Support for servers following SBSA/SBBR standards~~~ (done)
 * ~~~updated graphics drivers~~~ (done)
 * PVHVM and PVH
-* ~~~ARM64 ACPI~~~
+* ~~~ARM64 ACPI~~~ (done)
 * WireGuard
 * expand x86 intr masks to allow up to 64 interrupts per CPU and hence 48 MSI/MSI-X on cpu0
    [[http://mail-index.netbsd.org/current-users/2018/12/01/msg034728.html]]
@@ -69,3 +69,21 @@
 * rework semantics of threading operations in ptrace(2)
 
 ...
+
+## Release notes (top)
+
+* Support for Aarch64 (ARM 64-bit) machines. The aarch64 port should work on many Allwinner machines,
+SBSA/SBBR compatible servers. It supports multiple processors, including in a big.LITTLE configuration, ACPI and UEFI.
+It uses a single kernel to support a large amount of boards with the help of ACPI+UEFI or FDT.
+* Updated graphical acceleration support from Linux 4.4. Intel graphics including Kaby Lake.
+  Note: support for nVidia graphical cards was disabled. <!-- XXX, actually do this -->
+* bwfm(4) - Broadcom Full-MAC wireless driver (from OpenBSD)
+* ena(4) - Amazon.com Elastic Network Adapter (from FreeBSD)
+* ISDN support removed
+
+## Release notes (next)
+
+* GCC 6.5.0
+* LLVM 7.0.0
+* OpenSSL 1.1.1a
+* OpenSSH 7.8

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- wikisrc/releng/netbsd9.mdwn	7 Dec 2018 19:40:24 -0000	1.27
+++ wikisrc/releng/netbsd9.mdwn	7 Dec 2018 22:44:15 -0000	1.28
@@ -59,6 +59,8 @@
 * PVHVM and PVH
 * ~~~ARM64 ACPI~~~
 * WireGuard
+* expand x86 intr masks to allow up to 64 interrupts per CPU and hence 48 MSI/MSI-X on cpu0
+   [[http://mail-index.netbsd.org/current-users/2018/12/01/msg034728.html]]
 
 ## Nice to have, but likely won't be finished on time
 

cross off completed items for arm64, thanks jared.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- wikisrc/releng/netbsd9.mdwn	3 Dec 2018 01:12:56 -0000	1.26
+++ wikisrc/releng/netbsd9.mdwn	7 Dec 2018 19:40:24 -0000	1.27
@@ -53,11 +53,11 @@
 ## Nice to have
 
 * gcc 8+ from a sanitizers point of view
-* arm: GENERIC kernel config for armv7 boards.
-* arm64: Support for servers following SBSA/SBBR standards
+* ~~~arm: GENERIC kernel config for armv7 boards.~~~
+* ~~~arm64: Support for servers following SBSA/SBBR standards~~~
 * ~~~updated graphics drivers~~~ (done)
 * PVHVM and PVH
-* ARM64 ACPI
+* ~~~ARM64 ACPI~~~
 * WireGuard
 
 ## Nice to have, but likely won't be finished on time

improve
Index: wikisrc/security/kaslr.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/kaslr.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/security/kaslr.mdwn	28 Aug 2018 13:11:52 -0000	1.2
+++ wikisrc/security/kaslr.mdwn	6 Dec 2018 17:46:56 -0000	1.3
@@ -29,7 +29,7 @@
 Install this KASLR kernel:
 
 [[!template id=programlisting text="""
-# cp /path/to/your/kernel /netbsd_kaslr
+# cp /path/to/your/kaslr/kernel /netbsd_kaslr
 """]]
 
 Finally, add the following line in the `/boot.cfg` file:
@@ -44,13 +44,13 @@
 ---
 
 To use KASLR, just choose the "Boot KASLR" option in the menu at boot
-time. That's it!
+time. That's it! You are now using Kernel ASLR.
 
 Technical Details
 -----------------
 
 Kernel ASLR is applied by default in GENERIC on as many VM areas as possible.
-GENERIC_KASLR offers randomization of one more area: the Kernel Image.
+GENERIC_KASLR provides randomization of one more area: the Kernel Image.
 
 Table of what gets randomized:
 

Add WireGuard
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- wikisrc/releng/netbsd9.mdwn	24 Nov 2018 18:07:03 -0000	1.25
+++ wikisrc/releng/netbsd9.mdwn	3 Dec 2018 01:12:56 -0000	1.26
@@ -58,6 +58,7 @@
 * ~~~updated graphics drivers~~~ (done)
 * PVHVM and PVH
 * ARM64 ACPI
+* WireGuard
 
 ## Nice to have, but likely won't be finished on time
 

toast
Index: wikisrc/users/spz/sandbox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/sandbox.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/users/spz/sandbox.mdwn	10 Sep 2017 14:12:51 -0000	1.14
+++ wikisrc/users/spz/sandbox.mdwn	2 Dec 2018 14:41:03 -0000	1.15
@@ -1 +1 @@
-Sun Sep 10 16:09:35 CEST 2017
+Sun Dec  2 14:40:43 UTC 2018

Add BSDCan 2019.
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- wikisrc/events.mdwn	25 Oct 2018 17:34:50 -0000	1.70
+++ wikisrc/events.mdwn	30 Nov 2018 22:59:39 -0000	1.71
@@ -45,6 +45,18 @@
 possible audience.
 
 
+### `May 2019` - BSDCan 2019, Ottawa, Canada
+
+*May 15 - 18, 2019, University of Ottawa, Ottawa, Canada*
+
+[BSDCan](https://www.bsdcan.org/2019/), 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
 -----------
 

Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- wikisrc/ports/evbarm/allwinner.mdwn	25 Nov 2018 11:44:50 -0000	1.98
+++ wikisrc/ports/evbarm/allwinner.mdwn	26 Nov 2018 03:49:53 -0000	1.99
@@ -149,8 +149,8 @@
 Section "InputDevice"
         Identifier "Pinebook 1080p keyboard"
         Driver     "kbd"
-        XkbLayout  "us"
-        XkbVariant "altgr-intl"
+        Option     "XkbLayout"  "us"
+        Option     "XkbVariant" "altgr-intl"
 EndSection
 """]]
 

evbarm: address todo about earm meaning earmv5 (but not why)
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- wikisrc/ports/evbarm.mdwn	24 Nov 2018 22:46:45 -0000	1.67
+++ wikisrc/ports/evbarm.mdwn	25 Nov 2018 15:18:34 -0000	1.68
@@ -27,7 +27,7 @@
 There are
 four main variables: the word size, the instruction set, the
 endianness, and whether there is hardware floating point.  By default
-the CPU type is "earm", and this implies aarch32 (32-bit), \todo cpu
+the CPU type is "earm", and this implies aarch32 (32-bit), earmv5 cpu
 architecture, little endian (el when explicitly stated), and soft
 (Emulated) floating point.  Another example, suitable for Raspberry PI
 2, is earmv7hf, which is aarch32, the v7 instruction set, little

Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -r1.97 -r1.98
--- wikisrc/ports/evbarm/allwinner.mdwn	24 Nov 2018 19:13:29 -0000	1.97
+++ wikisrc/ports/evbarm/allwinner.mdwn	25 Nov 2018 11:44:50 -0000	1.98
@@ -139,6 +139,20 @@
 # /usr/bin/usbhidaction -c /etc/usbhidaction.conf -f /dev/uhid1 -i -p /var/run/usbhidaction-uhid1.pid 
 """]]
 
+## Pinebook keyboard
+
+The new 11" 1080p model has a slightly different keyboard layout to the 14".
+Using wscons it works perfectly, but using X the \ key next to left shift will display > when pressed.
+To solve this, you need to change the keyboard layout to altgr-intl. This can be done system wide by creating the file:
+
+[[!template  id=filecontent name="/etc/X11/xorg.conf.d/00-system-keyboard.conf" text="""
+Section "InputDevice"
+        Identifier "Pinebook 1080p keyboard"
+        Driver     "kbd"
+        XkbLayout  "us"
+        XkbVariant "altgr-intl"
+EndSection
+"""]]
 
 # Links
 

evbarm: explain aarch32 vs aarch64 a bit
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -r1.66 -r1.67
--- wikisrc/ports/evbarm.mdwn	24 Nov 2018 22:45:08 -0000	1.66
+++ wikisrc/ports/evbarm.mdwn	24 Nov 2018 22:46:45 -0000	1.67
@@ -75,7 +75,8 @@
 ### Relationship of MACHINE_ARCH to official ARM terminology
 
 Note that these are all little endian, and have big endian variants
-with a "eb" suffix.   
+with a "eb" suffix.  Unless otherwise noted, all use the A32 or
+aarch32 instruction set.
 
 [[!table data=<<EOT
 MACHINE_ARCH |bits | ARM architecture version            |ABI
@@ -85,7 +86,7 @@
 earmv5       |32   |armv5t                               |eabi
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi
-aarch64      |64   |armv8                                |\todo ? eabi
+aarch64      |64   |armv8 in aarch64 mode                |\todo ? eabi
 EOT]]
 
 \todo Explain why, if we have armv5, we still have earm as a MACHINE_ARCH.

evbarm: fix earm alias description
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- wikisrc/ports/evbarm.mdwn	24 Nov 2018 16:22:20 -0000	1.65
+++ wikisrc/ports/evbarm.mdwn	24 Nov 2018 22:45:08 -0000	1.66
@@ -79,8 +79,8 @@
 
 [[!table data=<<EOT
 MACHINE_ARCH |bits | ARM architecture version            |ABI
-arm          |32   |?                                    |oabi
-earm         |32   |armv4 (effectively an alias)         |eabi
+arm          |32   |\todo ?                              |oabi
+earm         |32   |alias for earmv5 (\todo why?)        |eabi
 earmv4       |32   |armv4 (no thumb, so ok on strongarm) |eabi
 earmv5       |32   |armv5t                               |eabi
 earmv6       |32   |armv6                                |eabi
@@ -88,7 +88,7 @@
 aarch64      |64   |armv8                                |\todo ? eabi
 EOT]]
 
-\todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
+\todo Explain why, if we have armv5, we still have earm as a MACHINE_ARCH.
 
 \todo Explain why aarch64 is a MACHINE_ARCH, when it seems like it
 should be something like armv8hf_64.

Update ref to 32-bit kernel config (GENERIC instead of SUNXI now), and update min. U-Boot version to 2018.05
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -r1.96 -r1.97
--- wikisrc/ports/evbarm/allwinner.mdwn	20 Nov 2018 12:05:00 -0000	1.96
+++ wikisrc/ports/evbarm/allwinner.mdwn	24 Nov 2018 19:13:29 -0000	1.97
@@ -45,7 +45,7 @@
 
 # Supported hardware
 
-Please refer to the [32-bit](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/SUNXI) or [64-bit](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/GENERIC64) kernel configs for the most up-to-date list of supported hardware.
+Please refer to the [GENERIC (32-bit)](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/GENERIC) or [GENERIC64 (64-bit)](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/GENERIC64) kernel configs for the most up-to-date list of supported hardware.
 
 <table>
   <thead>
@@ -94,7 +94,7 @@
 
 - Download or build **armv7.img** (32-bit) or **arm64.img** (64-bit) from NetBSD -current
 - Write the image to disk: **dd if=armv7.img of=/dev/rld0d bs=1m conv=sync**
-- Install a board-specific U-Boot (2017.07 or later) from pkgsrc to the SD card
+- Install a board-specific U-Boot (2018.05 or later) from pkgsrc to the SD card
   (the `u-boot-sunxi-with-spl.bin`-s are provided by `sysutils/u-boot-<boardname>` packages):
   **dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync**
 

Mark "plug kernel pointer leaks" as done. I can't immediately think of
other obvious sources of leak, but I fixed all those I was aware of,
so the issue can be considered as completed from a release PoV (not a
show-stopper).
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/releng/netbsd9.mdwn	20 Nov 2018 20:59:36 -0000	1.24
+++ wikisrc/releng/netbsd9.mdwn	24 Nov 2018 18:07:03 -0000	1.25
@@ -47,7 +47,7 @@
 * compiler-rt in the base with enabled features for Clang/LLVM
 * LVM mirror target
 * add NVMM
-* plug kernel pointer leaks
+* ~~~plug kernel pointer leaks~~~ (done)
 * fix Nouveau, some GPUs stopped working after the update
 
 ## Nice to have

We're already inside something triple-quoted (the template). Use a heredoc for the table data.
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -r1.64 -r1.65
--- wikisrc/ports/evbarm.mdwn	24 Nov 2018 16:18:34 -0000	1.64
+++ wikisrc/ports/evbarm.mdwn	24 Nov 2018 16:22:20 -0000	1.65
@@ -77,7 +77,7 @@
 Note that these are all little endian, and have big endian variants
 with a "eb" suffix.   
 
-[[!table data="""
+[[!table data=<<EOT
 MACHINE_ARCH |bits | ARM architecture version            |ABI
 arm          |32   |?                                    |oabi
 earm         |32   |armv4 (effectively an alias)         |eabi
@@ -86,7 +86,7 @@
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi
 aarch64      |64   |armv8                                |\todo ? eabi
-"""]]
+EOT]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 

Fix ikiwiki table directive, probably.
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- wikisrc/ports/evbarm.mdwn	24 Nov 2018 16:05:32 -0000	1.63
+++ wikisrc/ports/evbarm.mdwn	24 Nov 2018 16:18:34 -0000	1.64
@@ -77,7 +77,7 @@
 Note that these are all little endian, and have big endian variants
 with a "eb" suffix.   
 
-[[!table data=\"\"\"
+[[!table data="""
 MACHINE_ARCH |bits | ARM architecture version            |ABI
 arm          |32   |?                                    |oabi
 earm         |32   |armv4 (effectively an alias)         |eabi
@@ -86,7 +86,7 @@
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi
 aarch64      |64   |armv8                                |\todo ? eabi
-\"\"\"]]
+"""]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 

typo
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- wikisrc/ports/evbarm.mdwn	23 Nov 2018 11:58:27 -0000	1.62
+++ wikisrc/ports/evbarm.mdwn	24 Nov 2018 16:05:32 -0000	1.63
@@ -75,13 +75,13 @@
 ### Relationship of MACHINE_ARCH to official ARM terminology
 
 Note that these are all little endian, and have big endian variants
-with a "eb" sufix.   
+with a "eb" suffix.   
 
 [[!table data=\"\"\"
 MACHINE_ARCH |bits | ARM architecture version            |ABI
 arm          |32   |?                                    |oabi
 earm         |32   |armv4 (effectively an alias)         |eabi
-earmv4       |32   |armv4 (no thumb, so ok on strongarm) | eabi
+earmv4       |32   |armv4 (no thumb, so ok on strongarm) |eabi
 earmv5       |32   |armv5t                               |eabi
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi

Revert -r1.61, backslashes are probably needed because we are already in `"""'!
(This is mostly a revert to 1.60 except for a removal of probably extra `\'.)
Members: 
	ports/evbarm.mdwn:1.61->1.62 

Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- wikisrc/ports/evbarm.mdwn	23 Nov 2018 11:52:39 -0000	1.61
+++ wikisrc/ports/evbarm.mdwn	23 Nov 2018 11:58:27 -0000	1.62
@@ -77,7 +77,7 @@
 Note that these are all little endian, and have big endian variants
 with a "eb" sufix.   
 
-[[!table data="""
+[[!table data=\"\"\"
 MACHINE_ARCH |bits | ARM architecture version            |ABI
 arm          |32   |?                                    |oabi
 earm         |32   |armv4 (effectively an alias)         |eabi
@@ -86,7 +86,7 @@
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi
 aarch64      |64   |armv8                                |\todo ? eabi
-"""]]
+\"\"\"]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 

Avoid to backslash `"' for data in [[!table]], it should not be needed.
XXX: Maybe the table generation fails due missing Text::CSV and this commit
XXX: will probably not fix it!
Members: 
	ports/evbarm.mdwn:1.60->1.61 

Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- wikisrc/ports/evbarm.mdwn	22 Nov 2018 01:18:49 -0000	1.60
+++ wikisrc/ports/evbarm.mdwn	23 Nov 2018 11:52:39 -0000	1.61
@@ -77,7 +77,7 @@
 Note that these are all little endian, and have big endian variants
 with a "eb" sufix.   
 
-[[!table data=\"\"\\"
+[[!table data="""
 MACHINE_ARCH |bits | ARM architecture version            |ABI
 arm          |32   |?                                    |oabi
 earm         |32   |armv4 (effectively an alias)         |eabi
@@ -86,7 +86,7 @@
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi
 aarch64      |64   |armv8                                |\todo ? eabi
-\"\"\"]]
+"""]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 

evbarm: quote the table quotes, flailing
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- wikisrc/ports/evbarm.mdwn	22 Nov 2018 01:03:52 -0000	1.59
+++ wikisrc/ports/evbarm.mdwn	22 Nov 2018 01:18:49 -0000	1.60
@@ -77,7 +77,7 @@
 Note that these are all little endian, and have big endian variants
 with a "eb" sufix.   
 
-[[!table data="""
+[[!table data=\"\"\\"
 MACHINE_ARCH |bits | ARM architecture version            |ABI
 arm          |32   |?                                    |oabi
 earm         |32   |armv4 (effectively an alias)         |eabi
@@ -86,7 +86,7 @@
 earmv6       |32   |armv6                                |eabi
 earmv7       |32   |armv7                                |eabi
 aarch64      |64   |armv8                                |\todo ? eabi
-"""]]
+\"\"\"]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 

evbarm: update table
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- wikisrc/ports/evbarm.mdwn	22 Nov 2018 00:56:36 -0000	1.58
+++ wikisrc/ports/evbarm.mdwn	22 Nov 2018 01:03:52 -0000	1.59
@@ -78,18 +78,21 @@
 with a "eb" sufix.   
 
 [[!table data="""
-MACHINE_ARCH | 32/64 | ARM architecture version | ABI
-arm | 32 | ? | oabi
-earm | 32 | armv4 (effectively an alias) | eabi
-earmv4 | 32 | armv4 (no thumb, so ok on strongarm) | eabi
-earmv5 | 32 | armv5t | eabi
-earmv6 | 32 | armv6 | eabi
-earmv7 | 32 | armv7 | eabi
-aarch64 | 64 | armv8 | \todo ? eabi
+MACHINE_ARCH |bits | ARM architecture version            |ABI
+arm          |32   |?                                    |oabi
+earm         |32   |armv4 (effectively an alias)         |eabi
+earmv4       |32   |armv4 (no thumb, so ok on strongarm) | eabi
+earmv5       |32   |armv5t                               |eabi
+earmv6       |32   |armv6                                |eabi
+earmv7       |32   |armv7                                |eabi
+aarch64      |64   |armv8                                |\todo ? eabi
 """]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 
+\todo Explain why aarch64 is a MACHINE_ARCH, when it seems like it
+should be something like armv8hf_64.
+
 \todo Explain if MACHINE_ARCH values correspond to a particular
 argument to some CPU selection command in gcc (and/or clang).
 

evbarm: spiff up cpu type stuff
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- wikisrc/ports/evbarm.mdwn	21 Nov 2018 13:27:04 -0000	1.57
+++ wikisrc/ports/evbarm.mdwn	22 Nov 2018 00:56:36 -0000	1.58
@@ -29,7 +29,7 @@
 endianness, and whether there is hardware floating point.  By default
 the CPU type is "earm", and this implies aarch32 (32-bit), \todo cpu
 architecture, little endian (el when explicitly stated), and soft
-(emulated) floating point.  Another example, suitable for Raspberry PI
+(Emulated) floating point.  Another example, suitable for Raspberry PI
 2, is earmv7hf, which is aarch32, the v7 instruction set, little
 endian, and hardware floating point.
 
@@ -46,6 +46,53 @@
 with code in src/sys/arch/aarch64, but it is built as the evbarm port
 with aarch64 cpu type, and available as the alias evbarm64.
 
+Note that MACHINE_ARCH=aarch64 currently refers to the A64 instruction
+set and the aarch64 architecture, built for the armv8 architecture.
+(Note also that armv8 is the first architecture to support aarch64, so
+this will not be an issue until at least armv9.)
+
+#### ABI types
+
+There are two basic ABIs on ARM.  One, called oabi, assumed a
+particular kind of hardware floating point (FPA).  This results in
+faulting any floating-point instructions for kernel emulation on a
+vast number of CPus, which is very slow.  A newer one, called eabi,
+has two variants.  Both have stricter alignment rules, tending to 8
+byte rather than 4 bytes for 8-byte types (but actually read the specs
+if you care).  The one without "hf" emulates floating point without
+causing traps/emulation, and "hf" uses VFP instructions, which are
+present on modern CPUs. See the
+[TS-7200](https://wiki.embeddedarm.com/wiki/EABI_vs_OABI) and
+[Debian](https://wiki.debian.org/ArmEabiPort) documentation.
+
+Now, EABI is normal, and OABI is crufty.  The only real reason NetBSD
+retains OABI support is binary compatibility with older releases.  The
+"arm" and "armeb" MACHINE_ARCH targets are OABI; the rest of the
+targets, all having "earm" are EABI.
+
+\todo CHECK THIS: The "aarch64" MACHINE_ARCH target is an EABI variant.
+
+### Relationship of MACHINE_ARCH to official ARM terminology
+
+Note that these are all little endian, and have big endian variants
+with a "eb" sufix.   
+
+[[!table data="""
+MACHINE_ARCH | 32/64 | ARM architecture version | ABI
+arm | 32 | ? | oabi
+earm | 32 | armv4 (effectively an alias) | eabi
+earmv4 | 32 | armv4 (no thumb, so ok on strongarm) | eabi
+earmv5 | 32 | armv5t | eabi
+earmv6 | 32 | armv6 | eabi
+earmv7 | 32 | armv7 | eabi
+aarch64 | 64 | armv8 | \todo ? eabi
+"""]]
+
+\todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
+
+\todo Explain if MACHINE_ARCH values correspond to a particular
+argument to some CPU selection command in gcc (and/or clang).
+
 ### Kernels and userland
 
 The evbarm userland can be used on any system that can run code of the

add link to wikipedia
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- wikisrc/ports/evbarm.mdwn	11 Nov 2018 16:37:42 -0000	1.56
+++ wikisrc/ports/evbarm.mdwn	21 Nov 2018 13:27:04 -0000	1.57
@@ -22,7 +22,9 @@
 
 ### CPU types
 
-The evbarm port can be built with a variety of CPU options.  There are
+The evbarm port can be built with a variety of CPU options, corresponding to the
+[large array of ARM CPU architectures](https://en.wikipedia.org/wiki/ARM_architecture#Cores).
+There are
 four main variables: the word size, the instruction set, the
 endianness, and whether there is hardware floating point.  By default
 the CPU type is "earm", and this implies aarch32 (32-bit), \todo cpu

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/releng/netbsd9.mdwn	19 Nov 2018 22:25:53 -0000	1.23
+++ wikisrc/releng/netbsd9.mdwn	20 Nov 2018 20:59:36 -0000	1.24
@@ -34,8 +34,11 @@
    - ~~[[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]~~ (done)
    - ~~[[!template id=pr number=52614]] qemu virtual CD-ROM reports read errors since recent wdc changes~~ (done)
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
-* UBC using direct map working on amd64 and alpha
+* UBC using direct map working on amd64 and possibly alpha, aarch64
    - [[!template id=pr number=53124]] (FFS is slow because pmap_update doesn't scale)
+   - on alpha triggers machine check - verify on other machine?
+     [[https://mail-index.netbsd.org/source-changes-d/2018/05/22/msg010188.html]]
+   - aarch64 completely untested
 * XEN AVX working
    - ~~[[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set~~ (done)
 * ZFS

ETOO-/boot (be a bit more verbose about which /boot the kernel is loaded when
the installation to the hard disk is complete).
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	20 Nov 2018 12:41:35 -0000	1.17
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	20 Nov 2018 12:54:50 -0000	1.18
@@ -577,7 +577,7 @@
 
 Please remember that in the early boot phase, u-boot and `boot.scr`
 are loaded from the (u)SD card and it loads the kernel present in
-the `/boot` partition of the hard disk.
+the `/boot` partition of the hard disk (in our case "wd0e").
 
 
 # References

Add a `##' header to better distinguish the u-boot dance for booting from the
hard disk.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	20 Nov 2018 12:28:48 -0000	1.16
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	20 Nov 2018 12:41:35 -0000	1.17
@@ -553,6 +553,9 @@
 # umount /mnt
 """]]
 
+
+## NetBSD/evbarm 8.0 u-boot adjustments to boot from hard disk
+
 Finally we can prepare a u-boot script (`boot.scr`) to load the kernel from the
 SATA hard disk and boot it:
 

Add note about NetBSD 8.0 specific instructions (u-boot adjustments
for booting from SD card will not be needed in 9.0 thanks to (-current armv7.img
just works!))
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:50:11 -0000	1.15
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	20 Nov 2018 12:28:48 -0000	1.16
@@ -37,6 +37,13 @@
 # dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync
 """]]
 
+## NetBSD/evbarm 8.0 (and older) u-boot adjustments
+
+[[!template id=note text="""
+Please note that the following adjustments will not be needed in
+NetBSD-current and 9.0.
+"""]]
+
 NetBSD/evbarm 8.0 does not automatically boot on the BananaPI.
 We can use the following commands to boot from the (u)SD cards in u-boot:
 

Use the complete title
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -r1.95 -r1.96
--- wikisrc/ports/evbarm/allwinner.mdwn	20 Nov 2018 12:03:24 -0000	1.95
+++ wikisrc/ports/evbarm/allwinner.mdwn	20 Nov 2018 12:05:00 -0000	1.96
@@ -100,7 +100,8 @@
 
 If your SoC has a SATA controller and you would like to install on
 an hard disk and use a SD card only for u-boot please give a look
-to [[ports/evbarm/install_using_sysinst]].
+to
+[[NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card|ports/evbarm/install_using_sysinst]].
 
 # Tips and tricks
 
@@ -141,4 +142,4 @@
 
 # Links
 
-[[ports/evbarm/install_using_sysinst]]
+- [[NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card|ports/evbarm/install_using_sysinst]]

Add references to `NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB
stick or (u)SD card'
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- wikisrc/ports/evbarm/allwinner.mdwn	17 Nov 2018 11:44:28 -0000	1.94
+++ wikisrc/ports/evbarm/allwinner.mdwn	20 Nov 2018 12:03:24 -0000	1.95
@@ -98,6 +98,10 @@
   (the `u-boot-sunxi-with-spl.bin`-s are provided by `sysutils/u-boot-<boardname>` packages):
   **dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync**
 
+If your SoC has a SATA controller and you would like to install on
+an hard disk and use a SD card only for u-boot please give a look
+to [[ports/evbarm/install_using_sysinst]].
+
 # Tips and tricks
 
 ## Video overscan compensation
@@ -133,3 +137,8 @@
 # /usr/bin/usbhidaction -c /etc/usbhidaction.conf -f /dev/uhid0 -i -p /var/run/usbhidaction-uhid0.pid 
 # /usr/bin/usbhidaction -c /etc/usbhidaction.conf -f /dev/uhid1 -i -p /var/run/usbhidaction-uhid1.pid 
 """]]
+
+
+# Links
+
+[[ports/evbarm/install_using_sysinst]]

sed -i -Ee '/"""$/,/^"""/s/^$/ /' (add a space in programlisting to force
"screenshot" to 80x25).
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:44:51 -0000	1.14
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:50:11 -0000	1.15
@@ -113,16 +113,16 @@
 "Install NetBSD to hard disk":
 
 [[!template id=programlisting text="""
-
+ 
  NetBSD/evbarm 8.0
-
+ 
  This menu-driven tool is designed to help you install NetBSD to a hard disk,
  or upgrade an existing NetBSD system, with a minimum of work.
  In the following menus type the reference letter (a, b, c, ...) to select an
  item, or type CTRL+N/CTRL+P to select the next/previous item.
  The arrow keys and Page-up/Page-down may also work.
  Activate the current selection from the menu by typing the enter key.
-
+ 
  If you booted from a floppy, you may now remove the disk.
  Thank you for using NetBSD!
                +-----------------------------------------------+
@@ -136,9 +136,9 @@
                | f: Config menu                                |
                | x: Exit Install System                        |
                +-----------------------------------------------+
-
-
-
+ 
+ 
+ 
 """]]
 
 Before proceeding with the installation, if the hard disk had any important data
@@ -146,7 +146,7 @@
 we can safetely remove its data we can proceed:
 
 [[!template id=programlisting text="""
-
+ 
  You have chosen to install NetBSD on your hard disk.  This will change
  information on your hard disk.  You should have made a full backup before
  this procedure!  This procedure will do the following things:
@@ -154,10 +154,10 @@
          b) Create new BSD file systems
          c) Load and install distribution sets
          d) Some initial system configuration
-
+ 
  (After you enter the partition information but before your disk is changed,
  you will have the opportunity to quit this procedure.)
-
+ 
  Shall we continue?
                                +---------------+
                                | yes or no?    |
@@ -165,23 +165,23 @@
                                | a: No         |
                                |>b: Yes        |
                                +---------------+
-
-
-
-
-
-
-
+ 
+ 
+ 
+ 
+ 
+ 
+ 
 """]]
 
 Now we can see all the available disks. The hard disk attached via SATA is a
 120GB SSD recognized as `wd0`:
 
 [[!template id=programlisting text="""
-
+ 
  On which disk do you want to install NetBSD?
-
-
+ 
+ 
                      +-----------------------------------+
                      | Available disks                   |
                      |                                   |
@@ -189,21 +189,21 @@
                      | b: Extended partitioning          |
                      | x: Exit                           |
                      +-----------------------------------+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
 """]]
 
 We now need to edit MBR partition table. We will create two MBR partitions: the
@@ -211,18 +211,18 @@
 partition table":
 
 [[!template id=programlisting text="""
-
+ 
  We are now going to install NetBSD on the disk wd0.
-
+ 
  NetBSD requires a single partition in the disk's MBR partition table, this is
  split further by the NetBSD disklabel.  NetBSD can also access file systems
  in other MBR partitions.
-
+ 
  If you select 'Use the entire disk' then the previous contents of the disk
  will be overwritten and a single MBR partition used to cover the entire disk.
  If you want to install more than one operating system then edit the MBR
  partition table and create a partition for NetBSD.
-
+ 
  A few hundred MB is enough for a basic installation, but you should allow
  extra for additional software and user files.
  Allow at least 5GB if you want to build NetBSD itself.
@@ -232,21 +232,21 @@
                       |>a: Edit the MBR partition table |
                       | b: Use the entire disk          |
                       +---------------------------------+
-
-
-
-
-
+ 
+ 
+ 
+ 
+ 
 """]]
 
 First we select the second entry ("b"), set the "type:" to "NetBSD":
 
 [[!template id=programlisting text="""
-
+ 
  The Current MBR partition table is shown below.
  Flgs: a => Active partition, I => Install here.
  Select the partition you wish to change:
-
+ 
     Total disk size 114473 MB.
                +-----------------------------------------------------------+
     Start( MB) |>a:       type: unused                                     |
@@ -266,8 +266,8 @@
              | i: DOS FAT12                      |
              | &lt;: page up, &gt;: page down          |
              +-----------------------------------+
-
-
+ 
+ 
 """]]
 
 We reserve for the NetBSD MBR partition all the end of the disk,
@@ -276,11 +276,11 @@
 we will use it to install NetBSD ("install: Yes"):
 

(Diff truncated)
Add a space (s/^$/ /) in programlisting to try to force 80x25 "screenshots"
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:17:46 -0000	1.13
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:44:51 -0000	1.14
@@ -81,32 +81,32 @@
 latter ("Other"):
 
 [[!template id=programlisting text="""
-
-
-
-
-
-
-
-
-
-
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
                     +-------------------------------------+
                     | What kind of system do you have?    |
                     |                                     |
                     | a: Raspberry PI                     |
                     |>b: Other                            |
                     +-------------------------------------+
-
-
-
-
-
-
-
-
-
-
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
 """]]
 
 We want to install NetBSD/evbarm on the hard disk so let's select

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/releng/netbsd9.mdwn	19 Nov 2018 22:24:52 -0000	1.22
+++ wikisrc/releng/netbsd9.mdwn	19 Nov 2018 22:25:53 -0000	1.23
@@ -37,7 +37,7 @@
 * UBC using direct map working on amd64 and alpha
    - [[!template id=pr number=53124]] (FFS is slow because pmap_update doesn't scale)
 * XEN AVX working
-   - ~~[[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set~~
+   - ~~[[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set~~ (done)
 * ZFS
 * ~~~kASan for amd64~~~ (done)
 * ~~~kASan for aarch64~~~ (done)

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/releng/netbsd9.mdwn	16 Nov 2018 03:06:00 -0000	1.21
+++ wikisrc/releng/netbsd9.mdwn	19 Nov 2018 22:24:52 -0000	1.22
@@ -30,14 +30,14 @@
 * IPF/PF deprecation in favour of NPF
    - TODO: docs, what features to add to NPF ...
 * ATA/NCQ
-   - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
+   - ~~variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot~~ (done, waiting for confirmation)
    - ~~[[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]~~ (done)
    - ~~[[!template id=pr number=52614]] qemu virtual CD-ROM reports read errors since recent wdc changes~~ (done)
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
    - [[!template id=pr number=53124]] (FFS is slow because pmap_update doesn't scale)
 * XEN AVX working
-   - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
+   - ~~[[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set~~
 * ZFS
 * ~~~kASan for amd64~~~ (done)
 * ~~~kASan for aarch64~~~ (done)

Add References
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:06:47 -0000	1.12
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:17:46 -0000	1.13
@@ -572,4 +572,8 @@
 
 # References
 
-*TODOleot*: add a reference to the instructions shared via PR port-evbarm/50806.
+- [Installing NetBSD to HD/SSD on the Banana Pi](http://daemonforums.org/showthread.php?t=9652)
+  shows how to install NetBSD/evbarm 7.0 on a SATA hard disk by copying the
+  contents of (u)SD.
+- [Chapter 3. Example installation, The NetBSD Guide](https://www.netbsd.org/docs/guide/en/chap-exinst.html)
+  describes in details every steps of the NetBSD installation.

Add a short description of what we will do/discuss.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:00:10 -0000	1.11
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:06:47 -0000	1.12
@@ -4,6 +4,12 @@
 external media (SATA hard disk, USB stick or (u)SD card) using
 [[!template id=man name="sysinst" section="8"]].
 
+We will start by installing NetBSD/evbarm via `armv7.img` on a
+(u)SD card.  Then we will use
+[[!template id=man name="sysinst" section="8"]] to install
+NetBSD/evbarm on a SATA hard disk. The (u)SD card populated via
+`armv7.img` will then be used only in the early boot phase for u-boot.
+
 As practical example a BananaPI and a SATA hard disk will be used.
 However, the following instructions can be probably easily applied
 on other SoCs and medias with little adjustments.

Try to address most TODOs (document u-boot commands and boot.cmd on how to load
the kernel from the SATA hard disk).
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:49:42 -0000	1.10
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 22:00:10 -0000	1.11
@@ -64,8 +64,6 @@
 
 # Installing via sysinst(8)
 
-*TODOleot*: Document all sysinst(8) "screenshot"!
-
 Now that the SD card is populated with `armv7.img` we can login as `root` (by
 default the password is empty) and run `sysinst`:
 
@@ -532,14 +530,39 @@
 please give a look to
 [The NetBSD Guide](https://www.netbsd.org/docs/guide/en/chap-exinst.html#exinst-choose-media).
 
-*TODOleot*: add information how to populate `/boot` and prepare `boot.cmd`,
-`boot.scr`.
+When the installation is completed, back to the shell we can populate
+`/boot` partition of the hard disk ("wd0e") by just copying all
+files of the `/boot` partition of the (u)SD card (`armv7.img`):
 
 [[!template id=programlisting text="""
 # mount /dev/wd0e /mnt
 # cp -r /boot/* /mnt/
+# umount /mnt
+"""]]
+
+Finally we can prepare a u-boot script (`boot.scr`) to load the kernel from the
+SATA hard disk and boot it:
+
+[[!template id=programlisting text="""
+$ cat boot.cmd
+scsi scan
+scsi dev 0
+setenv kernel netbsd-BPI.ub
+fatload scsi 0:1 82000000 $kernel
+bootm 82000000 root=wd0a console=fb
+$ mkubootimage -A arm -n armv7 -T script boot.cmd boot.scr
 """]]
 
+...and copy them to the (u)SD `/boot`:
+
+[[!template id=programlisting text="""
+# cp boot.scr /boot
+"""]]
+
+Please remember that in the early boot phase, u-boot and `boot.scr`
+are loaded from the (u)SD card and it loads the kernel present in
+the `/boot` partition of the hard disk.
+
 
 # References
 

Add u-boot commands and boot.cmd example/notes on how to boot from the (u)SD.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:39:07 -0000	1.9
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:49:42 -0000	1.10
@@ -31,7 +31,35 @@
 # dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync
 """]]
 
-*TODOleot*: Adjust/provide u-boot incantantions to boot on a BPI
+NetBSD/evbarm 8.0 does not automatically boot on the BananaPI.
+We can use the following commands to boot from the (u)SD cards in u-boot:
+
+[[!template id=programlisting text="""
+mmc dev 0
+setenv kernel netbsd-BPI.ub
+fatload mmc 0:1 82000000 $kernel
+bootm 82000000 root=ld0a console=fb
+"""]]
+
+Or, to avoid typing them at every boot we can prepare an u-boot script via
+[[!template id=man name="mkubootimage" section="1"]].
+
+[[!template id=programlisting text="""
+$ cat boot.cmd
+mmc dev 0
+setenv kernel netbsd-BPI.ub
+fatload mmc 0:1 82000000 $kernel
+bootm 82000000 root=ld0a console=fb
+$ mkubootimage -A arm -n armv7 -T script boot.cmd boot.scr
+"""]]
+
+...and copy it on the populated (u)SD card:
+
+[[!template id=programlisting text="""
+# mount /dev/sd0e /mnt
+# cp /mnt/boot.scr /mnt/boot.scr.orig
+# cp boot.scr /mnt/
+"""]]
 
 
 # Installing via sysinst(8)

HTML entities should not used inside `...`
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:36:09 -0000	1.8
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:39:07 -0000	1.9
@@ -25,7 +25,7 @@
 """]]
 
 - Write u-boot to (u)SD card. `u-boot` images are provided by
-`sysutils/u-boot-&lt;boardname&gt;` packages, for example for Allwinner SoC:
+`sysutils/u-boot-<boardname>` packages, for example for Allwinner SoC:
 
 [[!template id=programlisting text="""
 # dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync

Use programlisting template, improve formatting and use `#' for commands that
should be probably invoked as root.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:18:08 -0000	1.7
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:36:09 -0000	1.8
@@ -12,19 +12,24 @@
 # Populating (u)SD card with `armv7.img`
 
 - Download or build `armv7.img`, e.g.:
-````
+
+[[!template id=programlisting text="""
 $ ftp http://cdn.NetBSD.org/pub/NetBSD/NetBSD-8.0/evbarm-earmv7hf/binary/gzimg/armv7.img.gz
 $ gunzip armv7.img.gz
-````
+"""]]
+
 - Write the image to (u)SD card:
-````
-$ dd if=armv7.img of=/dev/rsd0d bs=1m conv=sync
-````
+
+[[!template id=programlisting text="""
+# dd if=armv7.img of=/dev/rsd0d bs=1m conv=sync
+"""]]
+
 - Write u-boot to (u)SD card. `u-boot` images are provided by
 `sysutils/u-boot-&lt;boardname&gt;` packages, for example for Allwinner SoC:
-````
-$ dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync
-````
+
+[[!template id=programlisting text="""
+# dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync
+"""]]
 
 *TODOleot*: Adjust/provide u-boot incantantions to boot on a BPI
 

Document that we will use a BPI and a SATA hard disk (but probably all the
instructions can be applied with little adjustments on other SoCs and medias).
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:56:25 -0000	1.6
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 21:18:08 -0000	1.7
@@ -4,6 +4,10 @@
 external media (SATA hard disk, USB stick or (u)SD card) using
 [[!template id=man name="sysinst" section="8"]].
 
+As practical example a BananaPI and a SATA hard disk will be used.
+However, the following instructions can be probably easily applied
+on other SoCs and medias with little adjustments.
+
 
 # Populating (u)SD card with `armv7.img`
 

Add instructions about fetching and populating (u)SD card with armv7.img.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:18:00 -0000	1.5
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:56:25 -0000	1.6
@@ -7,7 +7,20 @@
 
 # Populating (u)SD card with `armv7.img`
 
-*TODOleot*: (mostly) copy-paste instructions from allwinner.mdwn
+- Download or build `armv7.img`, e.g.:
+````
+$ ftp http://cdn.NetBSD.org/pub/NetBSD/NetBSD-8.0/evbarm-earmv7hf/binary/gzimg/armv7.img.gz
+$ gunzip armv7.img.gz
+````
+- Write the image to (u)SD card:
+````
+$ dd if=armv7.img of=/dev/rsd0d bs=1m conv=sync
+````
+- Write u-boot to (u)SD card. `u-boot` images are provided by
+`sysutils/u-boot-&lt;boardname&gt;` packages, for example for Allwinner SoC:
+````
+$ dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync
+````
 
 *TODOleot*: Adjust/provide u-boot incantantions to boot on a BPI
 

Use HTML entities instead of `<' and `>'.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:14:38 -0000	1.4
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:18:00 -0000	1.5
@@ -210,7 +210,7 @@
              | g: Linux native                   |
              | h: Linux swap                     |
              | i: DOS FAT12                      |
-             | <: page up, >: page down          |
+             | &lt;: page up, &gt;: page down          |
              +-----------------------------------+
 
 

Improve formatting by using `programlisting' template.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:08:42 -0000	1.3
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:14:38 -0000	1.4
@@ -19,14 +19,14 @@
 Now that the SD card is populated with `armv7.img` we can login as `root` (by
 default the password is empty) and run `sysinst`:
 
-````
+[[!template id=programlisting text="""
 # sysinst
-````
+"""]]
 
 The first menu is about the system type (Respberry PI or Other), we select the
 latter ("Other"):
 
-````
+[[!template id=programlisting text="""
 
 
 
@@ -53,12 +53,12 @@
 
 
 
-````
+"""]]
 
 We want to install NetBSD/evbarm on the hard disk so let's select
 "Install NetBSD to hard disk":
 
-````
+[[!template id=programlisting text="""
 
  NetBSD/evbarm 8.0
 
@@ -85,13 +85,13 @@
 
 
 
-````
+"""]]
 
 Before proceeding with the installation, if the hard disk had any important data
 it is better to stop and doing a backup before proceeding. If it is empty and/or
 we can safetely remove its data we can proceed:
 
-````
+[[!template id=programlisting text="""
 
  You have chosen to install NetBSD on your hard disk.  This will change
  information on your hard disk.  You should have made a full backup before
@@ -118,12 +118,12 @@
 
 
 
-````
+"""]]
 
 Now we can see all the available disks. The hard disk attached via SATA is a
 120GB SSD recognized as `wd0`:
 
-````
+[[!template id=programlisting text="""
 
  On which disk do you want to install NetBSD?
 
@@ -150,13 +150,13 @@
 
 
 
-````
+"""]]
 
 We now need to edit MBR partition table. We will create two MBR partitions: the
 first one a FAT32 for `/boot` and the other for NetBSD. We select "Edit the MBR
 partition table":
 
-````
+[[!template id=programlisting text="""
 
  We are now going to install NetBSD on the disk wd0.
 
@@ -183,11 +183,11 @@
 
 
 
-````
+"""]]
 
 First we select the second entry ("b"), set the "type:" to "NetBSD":
 
-````
+[[!template id=programlisting text="""
 
  The Current MBR partition table is shown below.
  Flgs: a => Active partition, I => Install here.
@@ -214,14 +214,14 @@
              +-----------------------------------+
 
 
-````
+"""]]
 
 We reserve for the NetBSD MBR partition all the end of the disk,
 starting at 92MB (1MB that will be empty and 91MB that will be for
 the FAT32), we also select to make it active ("active: Yes") and
 we will use it to install NetBSD ("install: Yes"):
 
-````
+[[!template id=programlisting text="""
 
  The Current MBR partition table is shown below.
  Flgs: a => Active partition, I => Install here.
@@ -248,13 +248,13 @@
 
 
 
-````
+"""]]
 
 We now select the first partition ("a") and create a "Windows FAT32", starting
 at 1MB and ending at 92MB before the "NetBSD" partition. We also make it active
 ("active: Yes"):
 
-````
+[[!template id=programlisting text="""
 
  The Current MBR partition table is shown below.
  Flgs: a => Active partition, I => Install here.
@@ -281,11 +281,11 @@
 
 
 
-````
+"""]]
 
 Here the final MBR partition table:
 
-````
+[[!template id=programlisting text="""
 
  The Current MBR partition table is shown below.
  Flgs: a => Active partition, I => Install here.
@@ -312,12 +312,12 @@
 
 
 
-````
+"""]]
 
 Now that the MBR partition table is written we can proceed to set
 sizes of NetBSD partitions:
 
-````
+[[!template id=programlisting text="""
 
  NetBSD uses a BSD disklabel to carve up the NetBSD portion of the disk into
  multiple BSD partitions.  You must now set up your BSD disklabel.
@@ -344,11 +344,11 @@
 
 
 
-````
+"""]]
 
 We set the swap size to 4G and we reserve the rest of the space for "/":
 
-````
+[[!template id=programlisting text="""
 
  You can now change the sizes for the system partitions.  The default is to
  allocate all the space to the root file system.  However, you may wish to
@@ -375,11 +375,11 @@
 
 
 
-````
+"""]]
 
 The summary of the current BSD disklabel is:
 
-````
+[[!template id=programlisting text="""
 
  We now have your BSD disklabel partitions as:
  This is your last chance to change them.
@@ -406,14 +406,14 @@
 
 
 
-````
+"""]]
 
 We can adjust the disklabel, for example we can use FFSv2 for "/"

(Diff truncated)
Document all sysinst(8) steps illustrated.
Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 14:03:19 -0000	1.2
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 20:08:42 -0000	1.3
@@ -16,11 +16,16 @@
 
 *TODOleot*: Document all sysinst(8) "screenshot"!
 
+Now that the SD card is populated with `armv7.img` we can login as `root` (by
+default the password is empty) and run `sysinst`:
 
 ````
 # sysinst
 ````
 
+The first menu is about the system type (Respberry PI or Other), we select the
+latter ("Other"):
+
 ````
 
 
@@ -50,6 +55,9 @@
 
 ````
 
+We want to install NetBSD/evbarm on the hard disk so let's select
+"Install NetBSD to hard disk":
+
 ````
 
  NetBSD/evbarm 8.0
@@ -79,6 +87,10 @@
 
 ````
 
+Before proceeding with the installation, if the hard disk had any important data
+it is better to stop and doing a backup before proceeding. If it is empty and/or
+we can safetely remove its data we can proceed:
+
 ````
 
  You have chosen to install NetBSD on your hard disk.  This will change
@@ -108,6 +120,9 @@
 
 ````
 
+Now we can see all the available disks. The hard disk attached via SATA is a
+120GB SSD recognized as `wd0`:
+
 ````
 
  On which disk do you want to install NetBSD?
@@ -137,6 +152,10 @@
 
 ````
 
+We now need to edit MBR partition table. We will create two MBR partitions: the
+first one a FAT32 for `/boot` and the other for NetBSD. We select "Edit the MBR
+partition table":
+
 ````
 
  We are now going to install NetBSD on the disk wd0.
@@ -166,6 +185,8 @@
 
 ````
 
+First we select the second entry ("b"), set the "type:" to "NetBSD":
+
 ````
 
  The Current MBR partition table is shown below.
@@ -195,6 +216,11 @@
 
 ````
 
+We reserve for the NetBSD MBR partition all the end of the disk,
+starting at 92MB (1MB that will be empty and 91MB that will be for
+the FAT32), we also select to make it active ("active: Yes") and
+we will use it to install NetBSD ("install: Yes"):
+
 ````
 
  The Current MBR partition table is shown below.
@@ -224,6 +250,10 @@
 
 ````
 
+We now select the first partition ("a") and create a "Windows FAT32", starting
+at 1MB and ending at 92MB before the "NetBSD" partition. We also make it active
+("active: Yes"):
+
 ````
 
  The Current MBR partition table is shown below.
@@ -253,6 +283,8 @@
 
 ````
 
+Here the final MBR partition table:
+
 ````
 
  The Current MBR partition table is shown below.
@@ -282,6 +314,9 @@
 
 ````
 
+Now that the MBR partition table is written we can proceed to set
+sizes of NetBSD partitions:
+
 ````
 
  NetBSD uses a BSD disklabel to carve up the NetBSD portion of the disk into
@@ -311,6 +346,8 @@
 
 ````
 
+We set the swap size to 4G and we reserve the rest of the space for "/":
+
 ````
 
  You can now change the sizes for the system partitions.  The default is to
@@ -340,6 +377,8 @@
 
 ````
 
+The summary of the current BSD disklabel is:
+
 ````
 
  We now have your BSD disklabel partitions as:
@@ -369,6 +408,11 @@
 
 ````
 
+We can adjust the disklabel, for example we can use FFSv2 for "/"
+and for the disklabel "e" set its mount point to "/boot" in order
+that an `/etc/fstab` entry will be populated (please note
+that "/boot" will not be automatically mounted by default):
+
 ````
 
  We now have your BSD disklabel partitions as:
@@ -398,6 +442,13 @@
 
 ````
 
+We have finally ready to proceed with
+[[!template id=man name="sysinst" section="8"]] as usual and install
+the installation sets.  If you choose to install via FTP/HTTP please
+note that the "Binary set directory" needs to be adjusted from
+`/evbarm/binary/sets` to `/evbarm-earmv7hf/binary/sets` (it's
+missing an `-earmv7hf' due different evbarm-s):
+
 ````
 
  The following are the http site, directory, user, and password that will be
@@ -427,17 +478,18 @@
 
 ````
 
+The installation will proceed as usual and for more information
+please give a look to
+[The NetBSD Guide](https://www.netbsd.org/docs/guide/en/chap-exinst.html#exinst-choose-media).
+
+*TODOleot*: add information how to populate `/boot` and prepare `boot.cmd`,
+`boot.scr`.
+
 ````
 # mount /dev/wd0e /mnt
 # cp -r /boot/* /mnt/
 ````
 
-*TODOleot*: add a reference to The NetBSD Guide for further steps of the
-installation. 
-
-*TODOleot*: add information how to populate `/boot` and prepare `boot.cmd`,
-`boot.scr`.
-
 
 # References
 

Include all sysinst(8) "screenshots".
(Still completely not documented though!)
Members: 
	ports/evbarm/install_using_sysinst.mdwn:1.1->1.2 

Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 13:54:45 -0000	1.1
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	19 Nov 2018 14:03:19 -0000	1.2
@@ -14,7 +14,423 @@
 
 # Installing via sysinst(8)
 
-*TODOleot*: include all sysinst(8) "screenshot"
+*TODOleot*: Document all sysinst(8) "screenshot"!
+
+
+````
+# sysinst
+````
+
+````
+
+
+
+
+
+
+
+
+
+
+                    +-------------------------------------+
+                    | What kind of system do you have?    |
+                    |                                     |
+                    | a: Raspberry PI                     |
+                    |>b: Other                            |
+                    +-------------------------------------+
+
+
+
+
+
+
+
+
+
+
+````
+
+````
+
+ NetBSD/evbarm 8.0
+
+ This menu-driven tool is designed to help you install NetBSD to a hard disk,
+ or upgrade an existing NetBSD system, with a minimum of work.
+ In the following menus type the reference letter (a, b, c, ...) to select an
+ item, or type CTRL+N/CTRL+P to select the next/previous item.
+ The arrow keys and Page-up/Page-down may also work.
+ Activate the current selection from the menu by typing the enter key.
+
+ If you booted from a floppy, you may now remove the disk.
+ Thank you for using NetBSD!
+               +-----------------------------------------------+
+               | NetBSD-8.0 Install System                     |
+               |                                               |
+               |>a: Install NetBSD to hard disk                |
+               | b: Upgrade NetBSD on a hard disk              |
+               | c: Re-install sets or install additional sets |
+               | d: Reboot the computer                        |
+               | e: Utility menu                               |
+               | f: Config menu                                |
+               | x: Exit Install System                        |
+               +-----------------------------------------------+
+
+
+
+````
+
+````
+
+ You have chosen to install NetBSD on your hard disk.  This will change
+ information on your hard disk.  You should have made a full backup before
+ this procedure!  This procedure will do the following things:
+         a) Partition your disk
+         b) Create new BSD file systems
+         c) Load and install distribution sets
+         d) Some initial system configuration
+
+ (After you enter the partition information but before your disk is changed,
+ you will have the opportunity to quit this procedure.)
+
+ Shall we continue?
+                               +---------------+
+                               | yes or no?    |
+                               |               |
+                               | a: No         |
+                               |>b: Yes        |
+                               +---------------+
+
+
+
+
+
+
+
+````
+
+````
+
+ On which disk do you want to install NetBSD?
+
+
+                     +-----------------------------------+
+                     | Available disks                   |
+                     |                                   |
+                     |>a: wd0 (112G, SanDisk SDSSDA120G) |
+                     | b: Extended partitioning          |
+                     | x: Exit                           |
+                     +-----------------------------------+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+````
+
+````
+
+ We are now going to install NetBSD on the disk wd0.
+
+ NetBSD requires a single partition in the disk's MBR partition table, this is
+ split further by the NetBSD disklabel.  NetBSD can also access file systems
+ in other MBR partitions.
+
+ If you select 'Use the entire disk' then the previous contents of the disk
+ will be overwritten and a single MBR partition used to cover the entire disk.
+ If you want to install more than one operating system then edit the MBR
+ partition table and create a partition for NetBSD.
+
+ A few hundred MB is enough for a basic installation, but you should allow
+ extra for additional software and user files.
+ Allow at least 5GB if you want to build NetBSD itself.
+                      +---------------------------------+
+                      | Which would you like to do?     |
+                      |                                 |
+                      |>a: Edit the MBR partition table |
+                      | b: Use the entire disk          |
+                      +---------------------------------+
+
+
+
+
+
+````
+
+````
+
+ The Current MBR partition table is shown below.
+ Flgs: a => Active partition, I => Install here.
+ Select the partition you wish to change:
+
+    Total disk size 114473 MB.
+               +-----------------------------------------------------------+
+    Start( MB) |>a:       type: unused                                     |
+    ---------- | b:      start: 0 MB                                       |
+ a:            | c:       size: 0 MB                                       |
+>b:            | d:        end: 0 MB                                       |
+ c:            | e:     active: No                                         |
+ d:          +-----------------------------------+                         |
+ e: Change in| a: Don't change                   |linders/MB)              |
+ x: Partition| b: Delete partition               |                         |
+             |>c: NetBSD                         |-------------------------+
+             | d: Extended partition, LBA        |
+             | e: FreeBSD/386BSD                 |
+             | f: OpenBSD                        |
+             | g: Linux native                   |
+             | h: Linux swap                     |
+             | i: DOS FAT12                      |
+             | <: page up, >: page down          |
+             +-----------------------------------+
+
+
+````
+
+````
+
+ The Current MBR partition table is shown below.

(Diff truncated)
Add a wiki page intended to document step-by-step how to install NetBSD/evbarm
via sysinst(8) (starting from a (u)SD card populated via armv7.img).
Still completely full of TODO! (Hopefully they will be all addressed soon)
Members: 
	ports/evbarm/install_using_sysinst.mdwn:INITIAL->1.1 

--- /dev/null	2018-11-24 15:44:01.000000000 +0000
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	2018-11-24 15:44:06.000000000 +0000
@@ -0,0 +1,28 @@
+[[!meta title="NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card"]]
+
+In this document we will see step by step how to install NetBSD/evbarm on an
+external media (SATA hard disk, USB stick or (u)SD card) using
+[[!template id=man name="sysinst" section="8"]].
+
+
+# Populating (u)SD card with `armv7.img`
+
+*TODOleot*: (mostly) copy-paste instructions from allwinner.mdwn
+
+*TODOleot*: Adjust/provide u-boot incantantions to boot on a BPI
+
+
+# Installing via sysinst(8)
+
+*TODOleot*: include all sysinst(8) "screenshot"
+
+*TODOleot*: add a reference to The NetBSD Guide for further steps of the
+installation. 
+
+*TODOleot*: add information how to populate `/boot` and prepare `boot.cmd`,
+`boot.scr`.
+
+
+# References
+
+*TODOleot*: add a reference to the instructions shared via PR port-evbarm/50806.

Improve wording.
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- wikisrc/ports/evbarm/allwinner.mdwn	17 Nov 2018 11:13:16 -0000	1.93
+++ wikisrc/ports/evbarm/allwinner.mdwn	17 Nov 2018 11:44:28 -0000	1.94
@@ -95,7 +95,7 @@
 - Download or build **armv7.img** (32-bit) or **arm64.img** (64-bit) from NetBSD -current
 - Write the image to disk: **dd if=armv7.img of=/dev/rld0d bs=1m conv=sync**
 - Install a board-specific U-Boot (2017.07 or later) from pkgsrc to the SD card
-  (the `u-boot-sunxi-with-spl` are part of `sysutils/u-boot-<boardname>` packages):
+  (the `u-boot-sunxi-with-spl.bin`-s are provided by `sysutils/u-boot-<boardname>` packages):
   **dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync**
 
 # Tips and tricks

Add a note about u-boot-* packages (they are part of sysutils/u-boot-*).
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -r1.92 -r1.93
--- wikisrc/ports/evbarm/allwinner.mdwn	9 Jul 2018 11:54:39 -0000	1.92
+++ wikisrc/ports/evbarm/allwinner.mdwn	17 Nov 2018 11:13:16 -0000	1.93
@@ -94,7 +94,9 @@
 
 - Download or build **armv7.img** (32-bit) or **arm64.img** (64-bit) from NetBSD -current
 - Write the image to disk: **dd if=armv7.img of=/dev/rld0d bs=1m conv=sync**
-- Install a board-specific U-Boot (2017.07 or later) from pkgsrc to the SD card: **dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync**
+- Install a board-specific U-Boot (2017.07 or later) from pkgsrc to the SD card
+  (the `u-boot-sunxi-with-spl` are part of `sysutils/u-boot-<boardname>` packages):
+  **dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync**
 
 # Tips and tricks
 

Remove ptrace(2) plans from a blocker list for -9.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/releng/netbsd9.mdwn	15 Nov 2018 07:34:19 -0000	1.20
+++ wikisrc/releng/netbsd9.mdwn	16 Nov 2018 03:06:00 -0000	1.21
@@ -42,8 +42,6 @@
 * ~~~kASan for amd64~~~ (done)
 * ~~~kASan for aarch64~~~ (done)
 * compiler-rt in the base with enabled features for Clang/LLVM
-* address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
-* rework semantics of threading operations in ptrace(2)
 * LVM mirror target
 * add NVMM
 * plug kernel pointer leaks
@@ -61,5 +59,7 @@
 ## Nice to have, but likely won't be finished on time
 
 * merge pgoyette-compat
+* address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
+* rework semantics of threading operations in ptrace(2)
 
 ...

This project was done during GSoC 2018 by Keivan Motavalli.
(I have not added the `done_by=' tag because it still needs to be reviewed and
imported and added a note about that and removed the `[[!tag gsoc]]' because
despite the review work can be still considered a project it is not suitable for
a GSoC.)
Members: 
	projects/project/pkgsrc_config_vcs.mdwn:1.4->1.5 

Index: wikisrc/projects/project/pkgsrc_config_vcs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_config_vcs.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/pkgsrc_config_vcs.mdwn	24 Oct 2015 16:06:52 -0000	1.4
+++ wikisrc/projects/project/pkgsrc_config_vcs.mdwn	15 Nov 2018 12:07:58 -0000	1.5
@@ -40,7 +40,8 @@
 
 * extend functionality into additional VCS systems
 
+This project was done during Google Summer of Code 2018 by Keivan Motavalli
+[Configuration files versioning in pkgsrc](https://summerofcode.withgoogle.com/archive/2018/projects/4858976697057280/)
+project. At the moment the code need to be reviewed and imported in pkgsrc.
 """
 ]]
-
-[[!tag gsoc]]

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/releng/netbsd9.mdwn	15 Nov 2018 07:32:04 -0000	1.19
+++ wikisrc/releng/netbsd9.mdwn	15 Nov 2018 07:34:19 -0000	1.20
@@ -2,7 +2,7 @@
 
 ## PRs worth fixing
 
-(carried over from netbsd8)
+(carried over unclosed PRs from [[netbsd8]])
 
 * ~~[[!template id=pr number=53053]]: non-MULTIPROCESSOR hangs building Go~~ (still reproducable with newer go?)  
   [[!template id=pr number=53173]]: "go test net/http" locks up the machine (both PRs tied /!\ )

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/releng/netbsd9.mdwn	15 Nov 2018 07:25:39 -0000	1.18
+++ wikisrc/releng/netbsd9.mdwn	15 Nov 2018 07:32:04 -0000	1.19
@@ -19,6 +19,12 @@
 
 * [[!template id=pr number=53291]]: GPT prevents installation
 
+## Bug Bountys
+
+PRs in the above list marked with /!\ are show stoppers and have a bug bounty of $100 attached.
+If you find a solution for one of the marked issues that leads to closing of the PRs, we will get
+in touch with you.
+
 ## Features to finish/implement
 
 * IPF/PF deprecation in favour of NPF

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/releng/netbsd9.mdwn	11 Nov 2018 17:12:41 -0000	1.17
+++ wikisrc/releng/netbsd9.mdwn	15 Nov 2018 07:25:39 -0000	1.18
@@ -2,7 +2,22 @@
 
 ## PRs worth fixing
 
-* TBD
+(carried over from netbsd8)
+
+* ~~[[!template id=pr number=53053]]: non-MULTIPROCESSOR hangs building Go~~ (still reproducable with newer go?)  
+  [[!template id=pr number=53173]]: "go test net/http" locks up the machine (both PRs tied /!\ )
+
+* [[!template id=pr number=53016]]: Clock not stable /!\
+
+* [[!template id=pr number=53017]]: Kernel panics every now and then with "fpusave_lwp: did not" message
+
+* [[!template id=pr number=53155]]: Wedge after <12h uptime when >2 bnx network interfaces in use /!\
+
+* [[!template id=pr number=53161]]: ATF test runs leave a rump_server process around
+
+* [[!template id=pr number=53286]]: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case /!\
+
+* [[!template id=pr number=53291]]: GPT prevents installation
 
 ## Features to finish/implement
 

Index: wikisrc/releng/netbsd8.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd8.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/releng/netbsd8.mdwn	25 Oct 2018 15:58:33 -0000	1.52
+++ wikisrc/releng/netbsd8.mdwn	15 Nov 2018 07:23:12 -0000	1.53
@@ -14,7 +14,7 @@
 
 * ~~[[!template id=pr number=53096]]: netbsd-8 crash on heavy disk I/O~~ (done)
 
-* [[!template id=pr number=53053]]: non-MULTIPROCESSOR hangs building Go (still reproducable with newer go?)  
+* ~~[[!template id=pr number=53053]]: non-MULTIPROCESSOR hangs building Go~~ (still reproducable with newer go?)  
   [[!template id=pr number=53173]]: "go test net/http" locks up the machine (both PRs tied /!\ )
 
 * [[!template id=pr number=53016]]: Clock not stable /!\
@@ -33,7 +33,7 @@
 
 * ~~[[!template id=pr number=53292]]: uefi boot countdown is invisible~~
 
-* [[!template id=pr number=53294]]: ixg(4) stops receiving pkts /!\
+* ~~[[!template id=pr number=53294]]: ixg(4) stops receiving pkts~~
 
 ## Bug Bountys
 

new project for static locale
--- /dev/null	2018-11-24 15:44:01.000000000 +0000
+++ wikisrc/projects/project/static-locale.mdwn	2018-11-24 15:44:07.000000000 +0000
@@ -0,0 +1,25 @@
+[[!template id=project
+
+title="Statically linked locales for libc"
+
+contact="""
+[christos](mailto:christos@NetBSD.org),
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+duration="1 month"
+
+description="""
+The Citrus local code in NetBSD's libc stores the locale data and code
+in shared object files. Dynamic linking is used to load the code
+by name using dlopen(3). The static libc build (libc.a) can't use dlopen(3)
+to open locales and it only supports the C locale which is hard-coded.
+
+This project is about adding make(1) rules to compile all the locales in libc
+and code to select each one by name. The same technique is used in
+libpam (libpam.a).
+
+"""
+]]

ports: wording fix (thanks brook@)
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/ports.mdwn	11 Nov 2018 16:31:56 -0000	1.20
+++ wikisrc/ports.mdwn	11 Nov 2018 19:34:03 -0000	1.21
@@ -150,4 +150,4 @@
 cpu  | MACHINE_ARCH | uname -p | build.sh -a
 """]]
 
-Additonally, there are things referred to as ports which are not actually "uname -m" values, but are notably different than what would be expected from that port name.  One is xen, which is a system architecture variant of i386/amd64, and aarch64, which is CPU type variant of evbarm.
+Additonally, there are things referred to as ports which are not actually "uname -m" values, but are notably different than what would be expected from that port name.  One is xen, which is a system architecture variant of i386/amd64, and another is aarch64, which is a CPU type variant of evbarm.

nouveau not working on certain gpus
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/releng/netbsd9.mdwn	8 Nov 2018 08:33:44 -0000	1.16
+++ wikisrc/releng/netbsd9.mdwn	11 Nov 2018 17:12:41 -0000	1.17
@@ -26,6 +26,7 @@
 * LVM mirror target
 * add NVMM
 * plug kernel pointer leaks
+* fix Nouveau, some GPUs stopped working after the update
 
 ## Nice to have
 
@@ -33,7 +34,6 @@
 * arm: GENERIC kernel config for armv7 boards.
 * arm64: Support for servers following SBSA/SBBR standards
 * ~~~updated graphics drivers~~~ (done)
-  - investigate nouveau?
 * PVHVM and PVH
 * ARM64 ACPI
 

raspberry_pi: more 64-bit
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -r1.113 -r1.114
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	11 Nov 2018 16:48:03 -0000	1.113
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	11 Nov 2018 16:51:53 -0000	1.114
@@ -1,9 +1,11 @@
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
 
-This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards know to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
+This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards know to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.  This web page is 32-bit (aarch32) centric, as that has been until mid-2018 the only approach.
 
 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.  (This page assumes those using NetBSD 7 are using 7.2 or later, but note that everyone uses 8 or -current.)
 
+In mid-2018, -current gained support for 64-bit ARM (aarch64) support.
+
 [[images/raspberrypi.jpg]]
 
 [[!toc levels=2]]
@@ -36,6 +38,7 @@
  - RPI3+ 
  - RPI3 builtin bluetooth
  - RPI3 new SD host controller driver
+ - \todo Verify: RPI2-1.2 and RPI3 aarch64
 
 ## What needs documenting if it works
 

raspberry_pi: talk about 64 bit
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -r1.112 -r1.113
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Nov 2018 01:26:42 -0000	1.112
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	11 Nov 2018 16:48:03 -0000	1.113
@@ -1,6 +1,6 @@
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
 
-This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are supported.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
+This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards know to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
 
 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.  (This page assumes those using NetBSD 7 are using 7.2 or later, but note that everyone uses 8 or -current.)
 
@@ -48,6 +48,7 @@
  - USB (host); isochronous transfers.
  - RPI3, RPI0W builtin WiFi
  - RPI0W Bluetooth Low Energy (probably)
+ - aarch64 support is evolving very rapidly, and not yet recommended for production, largely because one must run -current.
 
 # CPU types
 
@@ -55,7 +56,8 @@
  - RPI0 uses "earmv6hf".
  - RPI0W uses "earmv6hf".
  - RPI2 uses "earmv7hf".
- - RPI3 uses "earmv7hf".
+ - RPI2-1.2 uses "earmv7hf" or "aarch64" (armv8 CPU hardware)
+ - RPI3 uses "earmv7hf" or "aarch64" (armv8 CPU hardware)
 
 Note that one can run a build of earmv6hf on the 2 and 3.  There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set.
 
@@ -63,7 +65,11 @@
 
 While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work.  Systems built with older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI.
 
-See also [[NetBSD/aarch64|aarch64]] for running the RPI2-1.2 and RPI3/RPI3+ in 64-bit mode.
+The RPI2-1.2 and RPI3 have an armv8 CPU that supports aarch64 (64-bit
+mode) in addition to aarch32 (regular 32-bit ARM).  This is supported,
+in -current only, by the "aarch64" MACHINE_ARCH of evbarm, also
+available in build.sh via the alias evbarm64.  This is sometimes
+referred to as [[NetBSD/aarch64|aarch64]].
 
 # Installation
 
@@ -214,6 +220,12 @@
 
 There is no well-defined USB enumeration order, so the preferred approach if one has multiple USB mass storage devices is to use named wedges in both fstab and cmdline.txt.
 
+## Split-mode aarch32/aarch64
+
+\todo Verify this, and add any necessary cautions about boot code.
+
+The aarch64 kernel can run aarch32 binaries, so one can boot a aarch64 kernel on a system with aarch32 userland.
+
 # X11 and GPU
 
 ## Video playback

evbarm: explain aarch64
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- wikisrc/ports/evbarm.mdwn	7 Nov 2018 15:09:41 -0000	1.55
+++ wikisrc/ports/evbarm.mdwn	11 Nov 2018 16:37:42 -0000	1.56
@@ -23,20 +23,26 @@
 ### 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 floating point.  By default the CPU type is "earm",
-and this implies little endian (el when explicitly stated), and soft
+four main variables: the word size, the instruction set, the
+endianness, and whether there is hardware floating point.  By default
+the CPU type is "earm", and this implies aarch32 (32-bit), \todo cpu
+architecture, 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 set, little endian,
-and hardware floating point.
+2, is earmv7hf, which is aarch32, the v7 instruction set, 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.
 
-Some processors can operate as arm or the 64-bit ARM variant, aarch64, which is supported by
-[[NetBSD/aarch64|aarch64]].
+Through NetBSD 8, the evbarm port has supported exclusively the
+aarch32 (32-bit CPU) sub-family of the ARM architecture.  Some
+processors, such as many supporting the armv8 CPU architecture, also
+support a 64-bit instruction set, referred to as aarch64.  This is
+sometimes referred to as a distinct port, [[NetBSD/aarch64|aarch64]],
+with code in src/sys/arch/aarch64, but it is built as the evbarm port
+with aarch64 cpu type, and available as the alias evbarm64.
 
 ### Kernels and userland
 

ports: clarify
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/ports.mdwn	11 Nov 2018 16:27:47 -0000	1.19
+++ wikisrc/ports.mdwn	11 Nov 2018 16:31:56 -0000	1.20
@@ -142,7 +142,7 @@
 
 ## Various ways of denoting ports and CPUs
 
-When discussing ports and CPUs, there are two concepts each of which have three ways of being named.  Strictly, the word port refers to the value shown by "uname -m", and typically corresponds to a directory under src/sys.  build.sh supports aliases, which are passed as if they were a port, but expand to a port and a cpu (MACHINE and MACHINE_ARCH); an example is evbearmv7hf-el which expands to the evbarm port and earmv7hf cpu.
+When discussing ports and CPUs, there are two concepts, each of which have three ways of being named.  Strictly, the word port refers to the value shown by "uname -m", and typically corresponds to a directory under src/sys.  build.sh supports aliases, which are passed as if they were a port, but expand to a port and a cpu (MACHINE and MACHINE_ARCH); an example is evbearmv7hf-el which expands to the evbarm port and earmv7hf cpu.
 
 [[!table data="""
 concept | /usr/share/mk variable | uname | build.sh
@@ -150,4 +150,4 @@
 cpu  | MACHINE_ARCH | uname -p | build.sh -a
 """]]
 
-Additonally, there are things referred to as ports which are notably different but are not actually "uname -m" values.  One is xen, which is a system architecture variant of i386/amd64, and aarch64, which is CPU type variant of evbarm.
+Additonally, there are things referred to as ports which are not actually "uname -m" values, but are notably different than what would be expected from that port name.  One is xen, which is a system architecture variant of i386/amd64, and aarch64, which is CPU type variant of evbarm.

ports: explain relationship of mk vairables, uname, build.sh.
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports.mdwn	26 Oct 2018 21:19:13 -0000	1.18
+++ wikisrc/ports.mdwn	11 Nov 2018 16:27:47 -0000	1.19
@@ -139,3 +139,15 @@
 vax		|II		|[[vax]]
 x86_64		|I		|[[amd64]] (Can also run i386 binaries), xen
 """]]
+
+## Various ways of denoting ports and CPUs
+
+When discussing ports and CPUs, there are two concepts each of which have three ways of being named.  Strictly, the word port refers to the value shown by "uname -m", and typically corresponds to a directory under src/sys.  build.sh supports aliases, which are passed as if they were a port, but expand to a port and a cpu (MACHINE and MACHINE_ARCH); an example is evbearmv7hf-el which expands to the evbarm port and earmv7hf cpu.
+
+[[!table data="""
+concept | /usr/share/mk variable | uname | build.sh
+port | MACHINE      | uname -m | build.sh -m
+cpu  | MACHINE_ARCH | uname -p | build.sh -a
+"""]]
+
+Additonally, there are things referred to as ports which are notably different but are not actually "uname -m" values.  One is xen, which is a system architecture variant of i386/amd64, and aarch64, which is CPU type variant of evbarm.

add link to bluetooth firmware
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/users/youri/pinebook-bugs.mdwn	9 Nov 2018 14:42:21 -0000	1.11
+++ wikisrc/users/youri/pinebook-bugs.mdwn	11 Nov 2018 14:23:46 -0000	1.12
@@ -28,6 +28,7 @@
   - Linux kernel support: <https://lkml.org/lkml/2018/7/25/267>
 - wifi support
 - bluetooth support
+  - firmware: <https://github.com/anarsoul/rtl8723bt-firmware>
 - suspend/resume support
 - sysinst support
 

fix link to "OpenLDAP Authentication on NetBSD" properly this time
Index: wikisrc/lighttpd_on_netbsd.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/lighttpd_on_netbsd.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/lighttpd_on_netbsd.mdwn	9 Nov 2018 19:36:13 -0000	1.3
+++ wikisrc/lighttpd_on_netbsd.mdwn	9 Nov 2018 19:39:38 -0000	1.4
@@ -90,7 +90,7 @@
 
 We will use OpenLdap. 
 
-First of all deploy a working ldap server, and populate it with the the users. For more information on this, read [[tutorials/openldap_authentication_on_netbsd|OpenLDAP Authentication on NetBSD]]. 
+First of all deploy a working ldap server, and populate it with the the users. For more information on this, read [[OpenLDAP Authentication on NetBSD|tutorials/openldap_authentication_on_netbsd]]. 
 
 Be sure to load mod_auth and include the following in your lighttpd.conf file: 
     

fix link to "OpenLDAP Authentication on NetBSD" tutorial
Index: wikisrc/lighttpd_on_netbsd.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/lighttpd_on_netbsd.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/lighttpd_on_netbsd.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/lighttpd_on_netbsd.mdwn	9 Nov 2018 19:36:13 -0000	1.3
@@ -90,9 +90,7 @@
 
 We will use OpenLdap. 
 
-First of all deploy a working ldap server, and populate it with the the users. For more information on this, read [OpenLDAP Authentication on NetBSD][10]. 
-
-   [10]: /OpenLDAP_Authentication_on_NetBSD (OpenLDAP Authentication on NetBSD)
+First of all deploy a working ldap server, and populate it with the the users. For more information on this, read [[tutorials/openldap_authentication_on_netbsd|OpenLDAP Authentication on NetBSD]]. 
 
 Be sure to load mod_auth and include the following in your lighttpd.conf file: 
     

sdmmc issue fixed
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/users/youri/pinebook-bugs.mdwn	1 Aug 2018 09:33:24 -0000	1.10
+++ wikisrc/users/youri/pinebook-bugs.mdwn	9 Nov 2018 14:42:21 -0000	1.11
@@ -14,7 +14,7 @@
 - <del>USB devices sometimes not detected after reboot</del>
   - urtwn(4) issue with 88EU support, workaround committed
 - Some USB keyboards cause problems (full sized FILCO tested)
-- sdmmc: DDR52 and HS200 are currently disabled in sunximmc(4) for Allwinner A64 due to issues on other boards. Need to track these down so we can run eMMC at full speed.
+- <del>sdmmc: DDR52 and HS200 are currently disabled in sunximmc(4) for Allwinner A64 due to issues on other boards. Need to track these down so we can run eMMC at full speed.</del>
 
 ## TODO
 

simplify given that Nagle is now fixed in the qemu mainline
Index: wikisrc/kernel_debugging_with_qemu.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kernel_debugging_with_qemu.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/kernel_debugging_with_qemu.mdwn	16 Mar 2018 15:29:26 -0000	1.16
+++ wikisrc/kernel_debugging_with_qemu.mdwn	9 Nov 2018 13:39:26 -0000	1.17
@@ -113,10 +113,8 @@
 """]]
 
 If the stack trace prints very slowly (like 30 seconds per stack
-frame), it's likely because you are using a version of qemu where
-the user-mode networking code fails to disable the Nagle algorithm.
-This is fixed in the qemu in pkgsrc, but you may run into it if your
-qemu is not installed via pkgsrc.
+frame), you are probably using an old version of qemu that fails
+to disable the Nagle algorithm.
 
 ## Qemu tips
 

raspberry_pi: typo, minor edit
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -r1.111 -r1.112
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 14:47:51 -0000	1.111
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Nov 2018 01:26:42 -0000	1.112
@@ -203,9 +203,9 @@
 
 The device boots by finding a file "bootcode.bin".   The primary location is a FAT32 partition on the uSD card, and an additional location is on a USB drive.  See the [upstream documentation on booting](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/) and read all the subpages.
 
-The standard approach is to use a uSD card, with a fdisk partition table containing a FAT32 partition marked active, and a NetBSD partition.  The NetBSD partition will then contain a disklabel, pointing to an FFS partition (a), a swap paritiion (b) and the FAT32 boot partition mounted as /boot (e).  The file /boot/cmdline.txt has a line to set the root partition.
+The standard approach is to use a uSD card, with a fdisk partition table containing a FAT32 partition marked active, and a NetBSD partition.  The NetBSD partition will then contain a disklabel, pointing to an FFS partition (a), a swap partition (b) and the FAT32 boot partition mounted as /boot (e).  The file /boot/cmdline.txt has a line to set the root partition.
 
-One wrinkle in the standard approach is that the disk layout is "boot swap /", but the NetBSD fdisk partition starts at the location of /.   The / partition can hold a disklabel, while swap cannot.   It is normal to have swap after / (and thus within the fdisk partition), but the arrangement used permits growing / on first boot, for the typical case where a larger uSD is used, compared to the minimum image size.
+One wrinkle in the standard approach is that the disk layout is "boot swap /", but the NetBSD fdisk partition starts at the location of /, so the swap partition is not within the NetBSD fdisk partition.  The / partition can hold a disklabel, while swap cannot.   It is normal to have swap after / (and thus within the fdisk partition), but the arrangement used permits growing / on first boot, for the typical case where a larger uSD is used, compared to the minimum image size.
 
 An alternate approach is to have the boot FAT32 partition as above, but to have the entire system including root on an external disk.  This is configured by changing root=ld0a to root=sd0a or root=dk0 (depending on disklabel/GPT).  Besides greater space, part of the point is to avoid writing to the uSD card.
 

aarch64+kasan done
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/releng/netbsd9.mdwn	25 Oct 2018 15:53:46 -0000	1.15
+++ wikisrc/releng/netbsd9.mdwn	8 Nov 2018 08:33:44 -0000	1.16
@@ -19,7 +19,7 @@
    - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
 * ZFS
 * ~~~kASan for amd64~~~ (done)
-* kASan for aarch64
+* ~~~kASan for aarch64~~~ (done)
 * compiler-rt in the base with enabled features for Clang/LLVM
 * address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
 * rework semantics of threading operations in ptrace(2)

Show the exact names of the qemu binaries used for evbarm emulations
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:49:13 -0000	1.54
+++ wikisrc/ports/evbarm.mdwn	7 Nov 2018 15:09:41 -0000	1.55
@@ -48,8 +48,8 @@
 
 anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.
 
- - evbarm-earmv7hf uses "qemu -M vexpress-a15"
- - evbarm-aarch64 uses "qemu -M virt"
+ - evbarm-earmv7hf uses "qemu-system-arm -M vexpress-a15"
+ - evbarm-aarch64 uses "qemu-system-aarch64 -M virt"
  - Information on how to test emulated versions of other specific hardware is welcome.
 
 ### Board specific information

fix markup
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:41:31 -0000	1.53
+++ wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:49:13 -0000	1.54
@@ -47,6 +47,7 @@
 ### anita and qemu
 
 anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.
+
  - evbarm-earmv7hf uses "qemu -M vexpress-a15"
  - evbarm-aarch64 uses "qemu -M virt"
  - Information on how to test emulated versions of other specific hardware is welcome.

fix evbarm link
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -r1.110 -r1.111
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 14:39:02 -0000	1.110
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 14:47:51 -0000	1.111
@@ -270,6 +270,6 @@
 
 ## Testing with anita and qemu
 
-See the anita section in [[the evbarm page|../evbarm]]
+See the anita section in the evbarm page.
 
 It is not currently known how to emulate a RPI in qemu, and therefore anita does not yet have support for this.  \todo Add a command-line example to run qemu emulating some RPI model.

fix markup
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:39:02 -0000	1.52
+++ wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:41:31 -0000	1.53
@@ -47,9 +47,9 @@
 ### anita and qemu
 
 anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.
-  - evbarm-earmv7hf uses "qemu -M vexpress-a15"
-  - evbarm-aarch64 uses "qemu -M virt"
-  - Information on how to test emulated versions of other specific hardware is welcome.
+ - evbarm-earmv7hf uses "qemu -M vexpress-a15"
+ - evbarm-aarch64 uses "qemu -M virt"
+ - Information on how to test emulated versions of other specific hardware is welcome.
 
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]

add more qemu/evbarm information
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:33:50 -0000	1.51
+++ wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:39:02 -0000	1.52
@@ -46,9 +46,10 @@
 
 ### anita and qemu
 
-anita can be used to test builds.  evbarm-earmv7hf uses "qemu -M
-vexpress-a15" and evbarm-aarch64 uses "qemu -M virt".  (Information on
-how to test emulated versions of other specific hardware is welcome.)
+anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.
+  - evbarm-earmv7hf uses "qemu -M vexpress-a15"
+  - evbarm-aarch64 uses "qemu -M virt"
+  - Information on how to test emulated versions of other specific hardware is welcome.
 
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -r1.109 -r1.110
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 01:10:59 -0000	1.109
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 14:39:02 -0000	1.110
@@ -270,10 +270,6 @@
 
 ## Testing with anita and qemu
 
-anita has support for evbarm.  Install qemu and dtb-arm-vexpress from pkgsrc.  Note that the release subdirectory should be evbarm-earmv6hf or evbarm-earmv7hf.
+See the anita section in [[the evbarm page|../evbarm]]
 
-\todo It is not currently known and documented how to configure qemu and anita to emulate a RPI in general or a specific RPI model.
-
-\todo Explain about how DTB works.
-
-\todo Give a command line example to run qemu (without anita).
+It is not currently known how to emulate a RPI in qemu, and therefore anita does not yet have support for this.  \todo Add a command-line example to run qemu emulating some RPI model.

evbarm: add qemu information
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- wikisrc/ports/evbarm.mdwn	30 Oct 2018 01:23:09 -0000	1.50
+++ wikisrc/ports/evbarm.mdwn	7 Nov 2018 14:33:50 -0000	1.51
@@ -44,6 +44,12 @@
 CPU type used for the build.  Typically, a particular board requires a
 kernel for that board.
 
+### anita and qemu
+
+anita can be used to test builds.  evbarm-earmv7hf uses "qemu -M
+vexpress-a15" and evbarm-aarch64 uses "qemu -M virt".  (Information on
+how to test emulated versions of other specific hardware is welcome.)
+
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone and BeagleBone Black|BeagleBone]]

Collapse entire "clang from base" into a link, that page now suggests mk.conf for both pkgsrc and base.
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:39:12 -0000	1.8
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	7 Nov 2018 07:05:07 -0000	1.9
@@ -2,18 +2,6 @@
 
 See [clang and the base system](../../clang/).
 
-When you have a NetBSD built with at least MKLLVM=yes, you can set
-
-    PKGSRC_COMPILER=       clang
-    CLANGBASE=             /usr
-    HAVE_LLVM=             yes
-
-in your /etc/mk.conf to use it. You must do that before building
-packages, especially libtool. It's usually fine to link binaries
-generated from gcc to those generated with clang or vice versa.
-
-\todo: Explain why HAVE_LLVM is set to use clang for pkgsrc.
-
 # Using clang from pkgsrc
 
 You can build clang from pkgsrc (lang/clang).  However, it needs

change . to :
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:59:14 -0000	1.9
+++ wikisrc/tutorials/clang.mdwn	7 Nov 2018 07:01:41 -0000	1.10
@@ -1,6 +1,6 @@
 Since NetBSD 6, the base system has included clang.  
 It works on ARM, PowerPC, x86, and possibly SPARC64, but is not built by default.  
-To use it, set in mk.conf.
+To use it, set in mk.conf:
 
     MKGCC=no
     MKLLVM=yes

mention PKGSRC_COPMILER which might be needed, markdown touchups
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:56:34 -0000	1.8
+++ wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:59:14 -0000	1.9
@@ -5,6 +5,7 @@
     MKGCC=no
     MKLLVM=yes
     HAVE_LLVM=yes
+    PKGSRC_COMPILER=clang
     CLANGBASE=/usr
 
 And run "build.sh release". This will apply for both pkgsrc and base.
@@ -13,9 +14,10 @@
 
 tunable                | explanation
 -----------------------|----------------------------------------------------
-MKGCC=no               | needed as building GCC alongside is not maintained.  
-MKLLVM=yes             | builds LLVM libraries.  
-HAVE_LLVM=yes          | controls clang being built  
+MKGCC=no               | needed as building GCC alongside is not maintained
+MKLLVM=yes             | builds LLVM libraries
+HAVE_LLVM=yes          | controls clang being built
+PKGSRC_COMPILER=clang  | instructs pkgsrc it's clang
 CLANGBASE=/usr         | instructs pkgsrc where to look for the compiler
 
 # status

omit link to pkgsrc clang page, actually a table, less text to -current builds, markdown touchups.
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:49:49 -0000	1.7
+++ wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:56:34 -0000	1.8
@@ -1,8 +1,6 @@
-This page explains how to use clang with the NetBSD base system.
-See also [how to use clang to build packages](../pkgsrc/clang/).
-
-Since NetBSD 6, the base system has included clang, but it is not
-built or used by default. To use it, set in mk.conf
+Since NetBSD 6, the base system has included clang.  
+It works on ARM, PowerPC, x86, and possibly SPARC64, but is not built by default.  
+To use it, set in mk.conf.
 
     MKGCC=no
     MKLLVM=yes
@@ -11,10 +9,10 @@
 
 And run "build.sh release". This will apply for both pkgsrc and base.
 
-This will work on ARM, PowerPC, x86, and possibly SPARC64.
 
-# Explanation
 
+tunable                | explanation
+-----------------------|----------------------------------------------------
 MKGCC=no               | needed as building GCC alongside is not maintained.  
 MKLLVM=yes             | builds LLVM libraries.  
 HAVE_LLVM=yes          | controls clang being built  
@@ -22,7 +20,4 @@
 
 # status
 
-On NetBSD-current, clang builds successfully on several architectures.
-These builds are with all three of the above flags enabled.
-
-https://releng.netbsd.org/builds/HEAD-llvm/
+[[NetBSD-current clang build status|https://releng.netbsd.org/builds/HEAD-llvm/]]

Attempt to make a markdown table
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:48:32 -0000	1.6
+++ wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:49:49 -0000	1.7
@@ -15,10 +15,10 @@
 
 # Explanation
 
-MKGCC=no                needed as building GCC alongside is not maintained.  
-MKLLVM=yes              builds LLVM libraries.  
-HAVE_LLVM=yes           controls clang being built  
-CLANGBASE=/usr          instructs pkgsrc where to look for the compiler
+MKGCC=no               | needed as building GCC alongside is not maintained.  
+MKLLVM=yes             | builds LLVM libraries.  
+HAVE_LLVM=yes          | controls clang being built  
+CLANGBASE=/usr         | instructs pkgsrc where to look for the compiler
 
 # status
 

try to use whitespace in markdown (probably won't work).
Separate explanation into its own section.
Members: 
	tutorials/clang.mdwn:1.5->1.6 

Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:46:18 -0000	1.5
+++ wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:48:32 -0000	1.6
@@ -13,10 +13,12 @@
 
 This will work on ARM, PowerPC, x86, and possibly SPARC64.
 
-MKGCC=no	needed as building GCC alongside is not maintained.  
-MKLLVM=yes	builds LLVM libraries.  
-HAVE_LLVM=yes	controls clang being built  
-CLANGBASE=/usr	instructs pkgsrc where to look for the compiler
+# Explanation
+
+MKGCC=no                needed as building GCC alongside is not maintained.  
+MKLLVM=yes              builds LLVM libraries.  
+HAVE_LLVM=yes           controls clang being built  
+CLANGBASE=/usr          instructs pkgsrc where to look for the compiler
 
 # status
 

Simplify use of this page (so the mk.conf hunk can be copied, and
then explain it). mention supported archs.
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/clang.mdwn	4 Jan 2018 20:45:01 -0000	1.4
+++ wikisrc/tutorials/clang.mdwn	7 Nov 2018 06:46:18 -0000	1.5
@@ -1,42 +1,22 @@
 This page explains how to use clang with the NetBSD base system.
 See also [how to use clang to build packages](../pkgsrc/clang/).
 
-\todo: review this entire page.
-
 Since NetBSD 6, the base system has included clang, but it is not
-built or used by default.
-
-\todo Explain if there are or aren't plans to enable it by default, or
-to switch, keeping in mind that compiler support varies by architecture.
-
-There are three steps that can be taken with clang; each depends on the previous.
-
-# Building clang
-
-To build clang as part of the build, set
+built or used by default. To use it, set in mk.conf
 
+    MKGCC=no
     MKLLVM=yes
-
-in mk.conf before running "build.sh release".
-
-This will build clang, which will appear in /usr/bin/clang and also
-build libraries that clang needs.  NetBSD itself will not be built
-with clang, but you will be able to use clang to build programs.
-
-# Using clang to build the NetBSD base system
-
-In addition, set
-
     HAVE_LLVM=yes
+    CLANGBASE=/usr
 
-to cause clang to be used instead of gcc.
-
-# Not building gcc
+And run "build.sh release". This will apply for both pkgsrc and base.
 
-On a system that builds clang and uses it to build the base system,
-you can refrain from building gcc, by additionally adding:
+This will work on ARM, PowerPC, x86, and possibly SPARC64.
 
-    MKGCC=no
+MKGCC=no	needed as building GCC alongside is not maintained.  
+MKLLVM=yes	builds LLVM libraries.  
+HAVE_LLVM=yes	controls clang being built  
+CLANGBASE=/usr	instructs pkgsrc where to look for the compiler
 
 # status
 

raspberry_pi: minor edits
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 00:56:20 -0000	1.108
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 01:10:59 -0000	1.109
@@ -52,10 +52,10 @@
 # CPU types
 
  - RPI1 uses "earmv6hf".
- - RPI0 uses "\todo".
+ - RPI0 uses "earmv6hf".
+ - RPI0W uses "earmv6hf".
  - RPI2 uses "earmv7hf".
  - RPI3 uses "earmv7hf".
- - RPI0W uses "\todo".
 
 Note that one can run a build of earmv6hf on the 2 and 3.  There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set.
 
@@ -126,7 +126,7 @@
 
 By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, mount the FAT32 partition on another system and edit cmdline.txt and remove '"console=fb"'.
 
- - Most (all?) USB-to-TTL serial adapters have wires for Tx, Rx and ground, and not RTS/CTS or other flow control lines.   Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration 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 have wires for TX, RX and ground, and not RTS/CTS or other flow control lines.   Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration 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 minicom, run "minicom -s" and set hardware flow control to "no".

raspberry_pi: drop sshramdisk \todo
I received email that it basically works, so there's no need to
question it.
Members: 
	ports/evbarm/raspberry_pi.mdwn:1.107->1.108 

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:42:38 -0000	1.107
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Nov 2018 00:56:20 -0000	1.108
@@ -144,8 +144,6 @@
  - Use ssh to login to the address you found with user "sysinst", and password "netbsd".
  - When installing, ensure that you enable DHCP and ssh, so that you can log in again after the system is installed.
 
-\todo Verify that the above is accurate and sufficient.
-
 The rpi_inst.img.gz image will only work for systems that use earmv6hf kernels (so not RPI2/3).  See [this port-arm message](https://mail-index.netbsd.org/port-arm/2017/08/18/msg004374.html) for details.
 
 ## Installation via ebijun's image

raspberry_pi: include more about rpi_inst
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -r1.106 -r1.107
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:36:39 -0000	1.106
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:42:38 -0000	1.107
@@ -113,7 +113,7 @@
 
 ## Preparing a uSD card
 
-Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example:
+Once you have rpi.img.gz (or rpi_inst for earmv6 boards), put it on a uSD card using gunzip and dd, for example:
 
  - gunzip rpi.img.gz
  - dd if=rpi.img of=/dev/disk1
@@ -146,6 +146,8 @@
 
 \todo Verify that the above is accurate and sufficient.
 
+The rpi_inst.img.gz image will only work for systems that use earmv6hf kernels (so not RPI2/3).  See [this port-arm message](https://mail-index.netbsd.org/port-arm/2017/08/18/msg004374.html) for details.
+
 ## Installation via ebijun's image
 
 As an alternative to the standard installation images, Jun Ebihara

raspberry_pi: enhance anita section
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -r1.105 -r1.106
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:34:51 -0000	1.105
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:36:39 -0000	1.106
@@ -272,6 +272,8 @@
 
 anita has support for evbarm.  Install qemu and dtb-arm-vexpress from pkgsrc.  Note that the release subdirectory should be evbarm-earmv6hf or evbarm-earmv7hf.
 
-\todo Explain how to select various RPI models to emulate.
+\todo It is not currently known and documented how to configure qemu and anita to emulate a RPI in general or a specific RPI model.
+
 \todo Explain about how DTB works.
+
 \todo Give a command line example to run qemu (without anita).

raspberry_pi: minor edits
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -r1.104 -r1.105
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:31:35 -0000	1.104
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:34:51 -0000	1.105
@@ -33,7 +33,7 @@
 
 ## NetBSD current
 
- - RPI3B+ 
+ - RPI3+ 
  - RPI3 builtin bluetooth
  - RPI3 new SD host controller driver
 
@@ -46,7 +46,8 @@
 ## What needs work
 
  - USB (host); isochronous transfers.
- - RPI3 builtin WiFi
+ - RPI3, RPI0W builtin WiFi
+ - RPI0W Bluetooth Low Energy (probably)
 
 # CPU types
 
@@ -194,7 +195,7 @@
 
 \todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain how to update a system (presumably /boot) from either an installed system's new firmware files, or the source tree.  Explain any particular cautions.
 
-Probably, for the RPI3B+, one needs to use -current, or use -8 with firmware from -current.  \todo Defuzz.
+Probably, for the RPI3+, one needs to use -current, or use -8 with firmware from -current.  \todo Defuzz.
 
 \todo Explain if using updated firmware from one branch (e.g. netbsd-current) on a system using a different branch (e.g. netbsd-8) is safe.  Explain if pullups are done to release branches with new firmware.
 

raspberry_pi: caution more strongly against 7
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -r1.103 -r1.104
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:29:26 -0000	1.103
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:31:35 -0000	1.104
@@ -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](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are supported.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
 
-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.  (This page assumes those using NetBSD 7 are using 7.2, or the netbsd-7 branch after mid 2018.)
+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.  (This page assumes those using NetBSD 7 are using 7.2 or later, but note that everyone uses 8 or -current.)
 
 [[images/raspberrypi.jpg]]
 

raspberry_pi: more hints from the list
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -r1.102 -r1.103
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:24:59 -0000	1.102
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:29:26 -0000	1.103
@@ -106,7 +106,7 @@
 Once you get to the releasedir, self-built and autobuild releases have the same structure.
 
  - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that will run on any of the RPI boards.
- - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the Raspberry Pi 2/3.
+ - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the RPI2 and RPI3 (and perhaps the CM3).  It also supports systems other than the RPI family.
 
 \todo Explain why there is no armv7_inst.gz.
 

raspberry_pi: enhance model descriptions
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:12:42 -0000	1.101
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:24:59 -0000	1.102
@@ -1,6 +1,6 @@
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
 
-This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
+This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are supported.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
 
 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.  (This page assumes those using NetBSD 7 are using 7.2, or the netbsd-7 branch after mid 2018.)
 
@@ -12,15 +12,10 @@
 
 # What works (and what doesn't yet)
 
-We use .e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
-
-
-\todo Add information  on Pi Zero and Pi Zero W.
-
 ## NetBSD 7 and NetBSD 8
 
- - RPI1, RPI2, RPI3 (except RPI3 builtin WiFi and bluetooth)
- - RPI0 and RPI0W are expected to work (as RPI3, no WiFi, but one needs fdt files \todo where from?)
+ - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth)
+ - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?)
  - multiple processors on RPI2/RPI3
  - boots normally to multiuser, with FAT32 boot partition on uSD
  - root filesystem can be uSD or USB-attached mass storage
@@ -42,6 +37,12 @@
  - RPI3 builtin bluetooth
  - RPI3 new SD host controller driver
 
+## What needs documenting if it works
+
+ - CM1
+ - CM3
+ - CM3lite
+
 ## What needs work
 
  - USB (host); isochronous transfers.
@@ -61,7 +62,7 @@
 
 While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work.  Systems built with older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI.
 
-See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
+See also [[NetBSD/aarch64|aarch64]] for running the RPI2-1.2 and RPI3/RPI3+ in 64-bit mode.
 
 # Installation
 

raspberry_pi: Edits based on hints from mlelstv@.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -r1.100 -r1.101
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 18:16:43 -0000	1.100
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 22:12:42 -0000	1.101
@@ -12,12 +12,16 @@
 
 # What works (and what doesn't yet)
 
+We use .e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
+
+
 \todo Add information  on Pi Zero and Pi Zero W.
 
 ## NetBSD 7 and NetBSD 8
 
- - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth)
- - multiple processors on 2/3
+ - RPI1, RPI2, RPI3 (except RPI3 builtin WiFi and bluetooth)
+ - RPI0 and RPI0W are expected to work (as RPI3, no WiFi, but one needs fdt files \todo where from?)
+ - multiple processors on RPI2/RPI3
  - boots normally to multiuser, with FAT32 boot partition on uSD
  - root filesystem can be uSD or USB-attached mass storage
  - serial or graphics console (with EDID query / parsing)
@@ -34,27 +38,28 @@
 
 ## NetBSD current
 
- - Raspberry Pi 3 builtin bluetooth
- - Raspberry Pi 3 new SD host controller driver
+ - RPI3B+ 
+ - RPI3 builtin bluetooth
+ - RPI3 new SD host controller driver
 
 ## What needs work
 
  - USB (host); isochronous transfers.
- - Raspberry Pi 3 builtin WiFi
+ - RPI3 builtin WiFi
 
 # CPU types
 
- - Raspberry Pi 1 uses "earmv6hf".
- - Raspberry Pi Zero uses "\todo".
- - Raspberry Pi 2 uses "earmv7hf".
- - Raspberry Pi 3 uses "earmv7hf".
- - Raspberry Pi Zero W uses "\todo".
+ - RPI1 uses "earmv6hf".
+ - RPI0 uses "\todo".
+ - RPI2 uses "earmv7hf".
+ - RPI3 uses "earmv7hf".
+ - RPI0W uses "\todo".
 
-Note that one can run earmv6hf userland code on the 2 and 3.  In theory the code compiled for earmv7hf will be faster. \todo Benchmark and explain.  \todo Explain if one can run the earmv6hf RPI2 kernel on RPI1.  \todo Explain if the earmv6hf rpi.img.gz will run on a RPI2/3.
+Note that one can run a build of earmv6hf on the 2 and 3.  There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set.
 
-\todo Explain if one can run "eb" variants.  (However, using eb is likely to find more bugs because almost everyone uses el.  That can either be a reason to run it or not run it.)
+In theory the code compiled for earmv7hf will be faster, but anecdotal experience is that it doesn't matter that much.
 
-\todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3.
+While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work.  Systems built with older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI.
 
 See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
 
@@ -188,6 +193,8 @@
 
 \todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain how to update a system (presumably /boot) from either an installed system's new firmware files, or the source tree.  Explain any particular cautions.
 
+Probably, for the RPI3B+, one needs to use -current, or use -8 with firmware from -current.  \todo Defuzz.
+
 \todo Explain if using updated firmware from one branch (e.g. netbsd-current) on a system using a different branch (e.g. netbsd-8) is safe.  Explain if pullups are done to release branches with new firmware.
 
 ## Booting
@@ -203,14 +210,10 @@
 A third approach, workable on the Pi 3 only, is to configure USB host booting (already enableed on the 3+; see the upstream documentation) and have the boot partition also on the external device.  In this case the external device must have an MBR because the hardware's first-stage boot does not have GPT support. In theory the [procedure to program USB host boot mode](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md) will function on a NetBSD system because the programming is done by bootcode.bin.
 \todo Confirm that putting program_usb_boot_mode=1 in config.txt and booting works to program the OTP bit.  Confirm that one can then boot NetBSD from external USB.
 
-\todo Explain USB enumeration and how to ensure that the correct boot and root devices are found if one has e.g. a small SSD for the system and a big disk.
+There is no well-defined USB enumeration order, so the preferred approach if one has multiple USB mass storage devices is to use named wedges in both fstab and cmdline.txt.
 
 # X11 and GPU
 
-## Console font
-
-Some find the default font to be too small.  \todo Give a link to the normal instructions on how to change it.
-
 ## Video playback
 Accelerated video playback is supported in NetBSD 7 with the [OMXPlayer](http://pkgsrc.se/multimedia/omxplayer) application and through GStreamer with the [omx](http://pkgsrc.se/multimedia/gst-plugins1-omx) plugin.
 

raspberry_pi: add qemu todo
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 18:13:17 -0000	1.99
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 18:16:43 -0000	1.100
@@ -269,3 +269,4 @@
 
 \todo Explain how to select various RPI models to emulate.
 \todo Explain about how DTB works.
+\todo Give a command line example to run qemu (without anita).

raspberry_pi: more firmware angst
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 18:03:21 -0000	1.98
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 18:13:17 -0000	1.99
@@ -188,6 +188,8 @@
 
 \todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain how to update a system (presumably /boot) from either an installed system's new firmware files, or the source tree.  Explain any particular cautions.
 
+\todo Explain if using updated firmware from one branch (e.g. netbsd-current) on a system using a different branch (e.g. netbsd-8) is safe.  Explain if pullups are done to release branches with new firmware.
+
 ## Booting
 
 The device boots by finding a file "bootcode.bin".   The primary location is a FAT32 partition on the uSD card, and an additional location is on a USB drive.  See the [upstream documentation on booting](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/) and read all the subpages.

raspberry_pi: Simplify wifi
Drop details not about the pi.
Members: 
	ports/evbarm/raspberry_pi.mdwn:1.97->1.98 

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -r1.97 -r1.98
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:36:23 -0000	1.97
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 18:03:21 -0000	1.98
@@ -149,6 +149,14 @@
 
  - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
 
+## Configuring 802.11
+
+After installation, the Ethernet will function as on any other NetBSD system; simply enable dhcpcd or configure a static address.  USB WiFi devices will also function as on any other NetBSD system; in addition to dhcpcd or static, configure and enable wpa_supplicant.
+
+Note that the built-in WiFi in the RPI3 is not yet supported.   USB WiFi interfaces (that work on NetBSD in general) should all work.  In particular, the following are known to work:
+
+ - urtwn0: Realtek (0xbda) 802.11n WLAN Adapter (0x8176), rev 2.00/2.00, addr 5, MAC/BB RTL8188CUS, RF 6052 1T1R
+
 ## Links
 
 The following pages have been published by NetBSD community members.  (Note that some of them are old.)
@@ -195,20 +203,6 @@
 
 \todo Explain USB enumeration and how to ensure that the correct boot and root devices are found if one has e.g. a small SSD for the system and a big disk.
 
-# Wireless Networking
-
-Note that the built-in WiFi in the RPI3 is not yet supported.   USB WiFi interfaces (that work on NetBSD in general) should all work.
-
- - A Realtek 802.11n USB adaptor configures as urtwn(4).
-   - Configure with wpa_supplicant in /etc/rc.conf -
-
-           ifconfig_urtwn0=dhcp
-           dhcpcd=YES
-           dhcpcd_flags="-q -b"
-           wpa_supplicant=YES
-           wpa_supplicant_flags="-B -i urtwn0 -c /etc/wpa_supplicant.conf"
-   - A sample wpa_supplicant.conf can be found at /usr/share/examples/wpa_supplicant/wpa_supplicant.conf
-
 # X11 and GPU
 
 ## Console font

remove comment converted to \todo
--- wikisrc/ports/evbarm/raspberry_pi/comment_18_8cd187a3b03cec17e897f29545fa6318._comment	2018-11-24 15:44:16.000000000 +0000
+++ /dev/null	2018-11-24 15:44:01.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="paul@f0c191796f3c93a5a8e45943cfbd5c6cdaa81a7a"
- nickname="paul"
- subject="Emulating RPI2 on Qemu?"
- date="2016-06-20T00:44:37Z"
- content="""
-Has anyone successfully gotten the RPI2 build running under the Qemu emulator?
-"""]]

remove addressed comment
--- wikisrc/ports/evbarm/raspberry_pi/comment_14_6a98b93491ed18d669785f0305b188a9._comment	2018-11-24 15:44:16.000000000 +0000
+++ /dev/null	2018-11-24 15:44:01.000000000 +0000
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="reemuskumar@9b54f47cb2494c139e103d068e790b4273edbd48"
- nickname="reemuskumar"
- subject="Want to Boot evbarmeb in Raspberry Pi"
- date="2016-02-27T12:40:58Z"
- content="""
-Hi,
-
-I want to boot my Raspberry Pi with evbarmeb. evbarmeb - is the Big-endian version of Netbsd, please correct me if I'm wrong.
-
-I'm not able to boot it. I tried the following steps to create the bootable SD Card :
-1. wget http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201602270000Z/evbarm-earmv7hfeb/binary/gzimg/armv7.img.gz
-2. gunzip armv7.img.gz
-3. dd if=armv7.img of=/dev/mmcblk0 bs=4M
-
-But I'm able to boot it with the normal evbarm7hf image. 
-
-Thanks,
-Reemus Kumar
-
-"""]]

Add a comment