Recent changes to this wiki:

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-12 01:37:01.000000000 +0000
+++ wikisrc/projects/project/static-locale.mdwn	2018-11-12 01:37:47.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-06 17:54:19.000000000 +0000
+++ /dev/null	2018-11-06 17:54: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-06 17:53:37.000000000 +0000
+++ /dev/null	2018-11-06 17:53:05.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
-
-"""]]

raspberry_pi: add eb comment
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -r1.96 -r1.97
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:34:03 -0000	1.96
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:36:23 -0000	1.97
@@ -52,6 +52,8 @@
 
 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.
 
+\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.)
+
 \todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3.
 
 See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.

raspberry_pi: add questions
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -r1.95 -r1.96
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:26:24 -0000	1.95
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:34:03 -0000	1.96
@@ -50,8 +50,11 @@
  - Raspberry Pi 3 uses "earmv7hf".
  - Raspberry Pi Zero W uses "\todo".
 
-Note that one can run earmv6hf code on the 2 and 3.  See also
-[[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
+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.
+
+\todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3.
+
+See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
 
 # Installation
 
@@ -72,7 +75,7 @@
 
 ## Getting bits to install
 
-You can either build a release yourself with build.sh, or get a release from the NetBSD HTTPS/FTP servers.  The bits from both sources should match, except for things like  timestamps, or because the sources are slightly different along branches.
+You can either build a release yourself with build.sh, or get a release from the NetBSD HTTPS/FTP servers.  The bits from both sources should match, except for things like  timestamps, or because the sources are from slightly different points along branches.
 
 ### Building yourself
 
@@ -86,14 +89,16 @@
 
 ### NetBSD autobuild HTTPS/FTP servers
 
-NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.  The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type.  It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it.  The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided.
+NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/).  The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type.  It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it.  The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided.
 
-An example URL, arguably the standard approach for beginners, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/
+An example URL, arguably the standard approach for first-time NetBSD/RPI users, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/
 
 ### release layout
 
+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, but is also faster than rpi.img.
+ - 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.
 
 \todo Explain why there is no armv7_inst.gz.
 

raspberry_pi: fix minor errors, tighten.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:18:38 -0000	1.94
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:26:24 -0000	1.95
@@ -66,23 +66,21 @@
 
 ## Choosing a version
 
-First, decide if you want to install a formal release (7.2 or 8.0), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  For people who don't know how to choose among those, 8.0 or netbsd-8 is probably best.
+First, decide if you want to install a formal release (7.2 or 8.0), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  For people who don't know how to choose among those, a recent build of netbsd-8 is probably best, with 8.0 the choice for those who value being at exactly a formal release.
 
 See also "ebijun's image", below, which is NetBSD-current and includes packages.
 
 ## Getting bits to install
 
-You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
-
-Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to be written to a uSD card, and has a FAT32 partition for booting.  In rpi.img.gz, there is also an FFS partition for NetBSD.
+You can either build a release yourself with build.sh, or get a release from the NetBSD HTTPS/FTP servers.  The bits from both sources should match, except for things like  timestamps, or because the sources are slightly different along branches.
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is equal to the second in effect, for RPI2/3.
+Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one each.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is equal to the second, for RPI2/3.  Note that the aliases start with "evb" while the MACHINE_ARCH values do not, and that aliases have "-el" or "-eb", while the MACHINE_ARCH values have no suffix or "eb".
 
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release
- - ./build.sh -m earmv7hf-el -u release
+ - ./build.sh -m evbearmv7hf-el -u release
 
 Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values for a MACHINE; see build.sh.  Use something like "evbarm-earmv7hf", so that 1) earvm6 and earmv7 don't collide and 2) anita will recognize it as a type of evbarm.
 
@@ -90,10 +88,14 @@
 
 NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.  The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type.  It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it.  The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided.
 
+An example URL, arguably the standard approach for beginners, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/
+
+### release layout
+
  - 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, but is also faster than rpi.img.
 
-An example URL, arguably the standard approach for beginners, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/
+\todo Explain why there is no armv7_inst.gz.
 
 ## Preparing a uSD card
 

raspberry_pi: Explain qemu some.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 14:10:38 -0000	1.93
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 17:18:38 -0000	1.94
@@ -84,7 +84,7 @@
  - ./build.sh -m evbarm -a earmv7hf -u release
  - ./build.sh -m earmv7hf-el -u release
 
-Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values on the same system; see build.sh.
+Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values for a MACHINE; see build.sh.  Use something like "evbarm-earmv7hf", so that 1) earvm6 and earmv7 don't collide and 2) anita will recognize it as a type of evbarm.
 
 ### NetBSD autobuild HTTPS/FTP servers
 
@@ -257,3 +257,10 @@
 - CPU frequency scaling
 
 Tests should be run on all of `rpi[0123]`.
+
+## 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.
+
+\todo Explain how to select various RPI models to emulate.
+\todo Explain about how DTB works.

prune addressed comment
--- wikisrc/ports/evbarm/raspberry_pi/comment_17_86103e0ef6127048abd4a4f1aac31003._comment	2018-11-06 14:11:34.000000000 +0000
+++ /dev/null	2018-11-06 14:11:03.000000000 +0000
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="991776254@ea9e6ab857ed376801070cbcff01c4baab1ec7c7"
- nickname="991776254"
- subject="Please tell me how to adjust console Font, it too small. "
- date="2016-05-21T02:04:09Z"
- content="""
-1. NetBSD rpi 7.99.29 NetBSD 7.99.29 (RPI.201605191830Z) evbarm
-
-2. I used 800*480 display. I have not hdmi display.
-3. I edit cmdline.txt, remove 'console=fb',display is black
-4. Please help me. Thanks.
-
-"""]]

raspberry_pi: add \todo about font
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -r1.92 -r1.93
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 14:08:48 -0000	1.92
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 14:10:38 -0000	1.93
@@ -200,7 +200,11 @@
            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
 
-# GPU
+# 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 todo about Zero/Zero W
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -r1.91 -r1.92
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:59:57 -0000	1.91
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 14:08:48 -0000	1.92
@@ -12,6 +12,8 @@
 
 # What works (and what doesn't yet)
 
+\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)
@@ -43,10 +45,10 @@
 # CPU types
 
  - Raspberry Pi 1 uses "earmv6hf".
- - Raspberry Pi 0 uses "\todo".
+ - Raspberry Pi Zero uses "\todo".
  - Raspberry Pi 2 uses "earmv7hf".
  - Raspberry Pi 3 uses "earmv7hf".
- - Raspberry Pi 0W uses "\todo".
+ - Raspberry Pi Zero W uses "\todo".
 
 Note that one can run earmv6hf code on the 2 and 3.  See also
 [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
@@ -250,5 +252,4 @@
 - Serial/framebuffer console
 - CPU frequency scaling
 
-Tests shoudl be run on all of `rpi[0123]`.
-
+Tests should be run on all of `rpi[0123]`.

prune addressed/integrated comments
--- wikisrc/ports/evbarm/raspberry_pi/comment_1_9d150dfe14d0b8ef00942c4528eed020._comment	2018-11-06 14:01:22.000000000 +0000
+++ /dev/null	2018-11-06 14:01:04.000000000 +0000
@@ -1,32 +0,0 @@
-[[!comment format=mdwn
- username="http://mat.clavid.com/"
- ip="46.29.255.44"
- subject="Solve installation step issue, and a few other things"
- date="2013-06-01T09:54:51Z"
- content="""
-Hello,
-
-it seems one of the first steps during the installation process is misleading, on the evbarm / raspberry pi platform.
-I ran into the issue, so as two mailing lists members recently did (and probably more people giving a try to netbsd on raspberry pi).
-
-I would like to edit this page http://wiki.netbsd.org/ports/evbarm/raspberry_pi/ and add a note about selecting the HEAD installation sets rather than the default:
-
-
-(A) IP Address during setup:
-As the net_rp.img install image uses DHCP at boot time, you will need to select DHCP during network configuration, or give your initial setup the very same IP received at boot time. You could change this later, but not on first boot and install run, else it will disconnect your remote connection.
-
-(B) Install sets:
-As the raspberry pi port is still not part the stable release, you will want to use the HEAD branch to download installation sets. 
-Have a look at http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/ and watch for the current YYYYMMDDHHMMZ branch. Use this timestap to adjust host and directory settings:
-
-a: Host nyftp.NetBSD.org
-b: Base directory pub/NetBSD-daily/HEAD/YYYYMMDDHHMMZ    (it will look like pub/NetBSD-daily/HEAD/201305220150Z)
-
-(C) Partitioning:
-During the partitioning process, do not delete or format the first MSDOS (FAT) partition, as the Raspberry pi firmware is hard coded to boot on the SDCAD / 1st MSDOS partition / Firmware updates and boot loader.
-
-When selecting partition types, remember you are using a SDCARD, nonvolatile flash memory wears slowly as writes are done. You may consider using non journaled filesystems (no log or LFS) and adjust mount options (noatime, nodevmtime). 
-
-Kind regards,
-Mat
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_2_ba8da9085ba45e3cc7506d2499cb63b3._comment	2018-11-06 14:01:23.000000000 +0000
+++ /dev/null	2018-11-06 14:01:04.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="mspo"
- ip="108.182.94.133"
- subject="thanks, Mat"
- date="2013-06-01T10:32:11Z"
- content="""
-Hey I integrated some of your notes into the page.
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_3_a94bded5b40cf5e232889708e8519339._comment	2018-11-06 14:01:23.000000000 +0000
+++ /dev/null	2018-11-06 14:01:04.000000000 +0000
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmrYoZc1GRmQ705rl0FoW5Sjj53FSeMqUs"
- nickname="Jonathan"
- subject="Installing packages"
- date="2015-01-04T22:48:08Z"
- content="""
-I have successfully installed NetBSD to my pi from the supplied images, but it is just the core system with no X server.  I am a relative newby to Linux, let alone BSD and am slowly working my way around it, but I am struggling with pkg_add because I can't find a source file to match...
-
-I downloaded rpi.img.gz from here:
-http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201501031030Z/evbarm-earmv6hf/binary/gzimg/
-
-I followed the instructions on this page, but fall down when trying to add packages
-
-but when following the instructions here: https://www.netbsd.org/docs/pkgsrc/using.html
-and here: http://www.netbsd.org/docs/guide/en/chap-boot.html
-
-I cannot find a matching distribution.
-
-uname -a reports:
-NetBSD rpi 7.0_BETA NetBSD 7.0_BETA (RPI_201501031030Z) evbarm
-
-but the closest I can get is
-ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/evbarm/6.1
-
-Should I be looking elsewhere for the repository?
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_4_2aa63cae578e7b4f938ec77a36d5e647._comment	2018-11-06 14:01:23.000000000 +0000
+++ /dev/null	2018-11-06 14:01:04.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawljikmK5KwP_VFyYnoEsWkb1Za2fYGeUkw"
- nickname="Nick"
- subject="@Jonathan"
- date="2015-01-05T17:06:33Z"
- content="""
-You might want to check out installing pkgsrc and building your own packages - this article may help <http://www.cambus.net/netbsd-on-the-raspberry-pi/>
-"""]]

raspberry_pi: mention noatime
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -r1.90 -r1.91
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:54:26 -0000	1.90
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:59:57 -0000	1.91
@@ -60,6 +60,8 @@
 
 A 2 GB card is the smallest workable size, and the installation image will fit.  After the first boot, the system resizes the NetBSD root partition to fill the card.  Note that swap is after /boot and before /, and not contained in the NetBSD fdisk partition.  However, if you don't try to change the partition structure, this should not cause you any trouble.
 
+Note that SD cards generally have limited write tolerance, so you may wish to disable atime updates via the noatime option, as is done by the default installation.
+
 ## Choosing a version
 
 First, decide if you want to install a formal release (7.2 or 8.0), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  For people who don't know how to choose among those, 8.0 or netbsd-8 is probably best.

raspberry_pi: Add link from comment about to be deleted
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:51:04 -0000	1.89
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:54:26 -0000	1.90
@@ -136,6 +136,12 @@
 
  - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
 
+## Links
+
+The following pages have been published by NetBSD community members.  (Note that some of them are old.)
+
+ - https://www.cambus.net/netbsd-on-the-raspberry-pi/
+
 # Maintaining a system
 
 ## vcgencmd

raspberry_pi: spiff up boot/console/ssh section
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -r1.88 -r1.89
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:31:59 -0000	1.88
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:51:04 -0000	1.89
@@ -98,31 +98,33 @@
  - gunzip rpi.img.gz
  - dd if=rpi.img of=/dev/disk1
 
-### Serial Console
+## Console approaches
+
+The standard approach is to use a USB keyboard and an HDMI monitor for installation.
 
-By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then
-edit cmdline.txt and remove '"console=fb"'.
+### Serial Console
 
- - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
+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"'.
 
-   In Kermit, the command is "set flow 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 minicom, run "minicom -s" and set hardware flow control to "no"
+   - In Kermit, the command is "set flow none".
+   - In minicom, run "minicom -s" and set hardware flow control to "no".
 
-### Enabling ssh
+### Enabling ssh for installation without any console
 
-If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address, you will have to wait for the partition resizing and reboot.
+If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, you can edit the configuration of a uSD card before booting.   On another computer, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address (e.g. from DHCP server logs), you will have to wait for the partition resizing and reboot.
 
 ### Installation with sshramdisk image
 
-build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
+build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console, when built for earmv6hf.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
+
+ - Connect an Ethernet cable from the RPI to a LAN with a DHCP server, and another host you can use for ssh.
+ - Power on the RPI, and wait.  Watch the logs on the DHCP server, and find the IP address assigned to the RPI.
+ - 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.
 
- - Ensure that you have a lan with a DHCP server.
- - Connect an Ethernet cable from the RPI to the LAN.
- - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
-   - Be careful to note the ip address given during DHCP so you don't lose your connection
-   - Also for after the sysinst is done and the system reboots
- - sysinst started!
+\todo Verify that the above is accurate and sufficient.
 
 ## Installation via ebijun's image
 

prune addressed/obsolete comments
--- wikisrc/ports/evbarm/raspberry_pi/comment_13_1441d530a7ae119ed06b642bcf692ed6._comment	2018-11-06 13:38:00.000000000 +0000
+++ /dev/null	2018-11-06 13:37:11.000000000 +0000
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="aggaz@10787e7d451eca8e07078b14fc176f8edd2248c5"
- nickname="aggaz"
- subject="Install earm6hf on RPi Mod B Ver 1"
- date="2016-01-10T21:33:24Z"
- content="""
-Hello,
-
-I am a total NetBSD-noob and today I figured out how to install NetBSD on my RPi Mod B Ver 1.
-
-I used rpi_inst.img and in order to make pkgin work I had to edit the default ftp repositories.
-
-Browsing the FTP, I saw that inside the following dir:
-ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/
-
-there was not a dir named 7.0 so I used the only path that made me install pkgin, this one:
-ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/7.0_2015Q1/All/
-
-Now I am trying to install vim, but inside this dir there is not a vim package.
-However I can see two vim packages, one for each of these paths:
-
-ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/7.0_2015Q2/All/
-ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/7.0_2015Q3/All/
-
-Said that, my question is:
-Did I messed up the selection of the mirror?
-Why only the first path had all the dependecies needed by pkgin? (I am sorry I do not remember which package was missing)
-Can I (and should I) add all the three paths to install other packages?
-
-For those interested, I wrote down all the steps I followed during installation.
-https://blog.apsu.it/netbsd-rpib1-install
-
-Regards
-agz
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_5_e342e8f4927d08f4a1f9e22df21d1930._comment	2018-11-06 13:38:00.000000000 +0000
+++ /dev/null	2018-11-06 13:37:11.000000000 +0000
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmuLc-YNA2_8q6AkCIS1Ca0eims4YukCvw"
- nickname="Youri"
- subject="NetBSD error"
- date="2015-03-22T14:36:38Z"
- content="""
-if you get the following error while trying to fetch sets;
-
-ftp: Can't LOOKUP `nyftp.NetBSD.org:http': Temporary failure in name resolution
-
-
-Please use the nyftp's IP address instead: 128.59.23.63
-
-As reported by http://stackoverflow.com/questions/27690637/installing-netbsd-sets-via-http-on-raspberry-pi-fails
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_6_6a8a5c909e9d832060e5e95a9094d4f4._comment	2018-11-06 13:38:00.000000000 +0000
+++ /dev/null	2018-11-06 13:37:11.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmqO-DKfMvJ8kKGWNdYg0fAZOFPs0Mx73I"
- nickname="alakesh"
- subject="Development environment for compiling netbsd for raspberry pi 2"
- date="2015-04-05T17:53:36Z"
- content="""
-Can someone please post link to netbsd 7.0 sources? I want to compile latest netbsd for my raspberry pi 2 board.
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_7_7fbf9e5dada4e180566e226e89de346f._comment	2018-11-06 13:38:00.000000000 +0000
+++ /dev/null	2018-11-06 13:37:11.000000000 +0000
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/zbnUQNAbxcHRnhYvX5QUZJCbhUkH#18c66"
- nickname="Tobias N. Sasse"
- subject="firmware update"
- date="2015-04-15T12:57:42Z"
- content="""
-Can anyone explain if all files (including the subdirectory overlays/ ) need to be copied?
-\"Copy all files except 'kernel*.img' into /boot and reboot\"
-
-Or would a subset be sufficient?
-
-Thanks very much
--- Tobi
-"""]]

raspberry_pi: enhance firmware update section
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -r1.87 -r1.88
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:27:25 -0000	1.87
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:31:59 -0000	1.88
@@ -157,7 +157,7 @@
 
 A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers.  This section is about updating a system's firmware from the firmware in a version of NetBSD.
 
-\todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain any particular cautions.
+\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.
 
 ## Booting
 

\todo regularization
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 03:13:59 -0000	1.86
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 13:27:25 -0000	1.87
@@ -157,7 +157,7 @@
 
 A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers.  This section is about updating a system's firmware from the firmware in a version of NetBSD.
 
-TODO: Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain any particular cautions.
+\todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain any particular cautions.
 
 ## Booting
 

drop addressed comments
--- wikisrc/ports/evbarm/raspberry_pi/comment_12_5be5b738969b237e6f829234e4273873._comment	2018-11-06 12:41:35.000000000 +0000
+++ /dev/null	2018-11-06 12:41:04.000000000 +0000
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="ax0n@148d6d53e1d08a16f4203b4bf5de5f5d1d0f9094"
- nickname="ax0n"
- subject="NetBSD working on the Raspberry Pi Zero"
- date="2016-01-02T03:04:01Z"
- content="""
-Trying to boot the latest snapshot on my Pi Zero resulted in 8 flashes of the OK/ACT LED (bootcode.bin and/or start.elf problems, according to the documentation).
-
-This image boots fine on my Pi B+ and Pi 2.
-
-I over-wrote bootcode.bin, start.elf and start_cd.elf on the freshly imaged SD card from an Arch Linux MicroSD that works in the Pi Zero. It now boots. I don't know if these are exactly the correct files, but I suspect they likely require updating in the base image. 
-
-I've included MD5 sums of the files for your convenience:
-From the NetBSD Image (20151231): 
-MD5 (bootcode.bin) = 9a4ad6a12ad7dc1aae279888c25d2252
-MD5 (start.elf) = a2c4b9ea3ae986f88ea01e05bef46904
-MD5 (start_cd.elf) = 85924312c9b51d1ef5b7ca301bb18d54
-
-Files I copied over that make it bootable (from my Arch Linux Pi Zero environment):
-MD5 (bootcode.bin) = 6cc6560c0178c10928d14b8768969dab
-MD5 (start.elf) = f5b2a422d863efe5d47b1ac291ccaa3a
-MD5 (start_cd.elf) = f0dfc1462c5d9b003b64428fd52406ed
-
-Hope this helps!
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_16_76d86737b956deadfb9ca4ede96641c4._comment	2018-11-06 12:41:35.000000000 +0000
+++ /dev/null	2018-11-06 12:41:04.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="vkhutkO@025be5b36b030bb304e605fa0c3d03f8695aaf9d"
- nickname="vkhutkO"
- subject="Raspberry PI 3 support"
- date="2016-04-27T09:10:52Z"
- content="""
-I want to lift-up this theme. This RPi uses slightly different Broadcom chip and I expected, that either evbarm6hf or evbarm7hf kernels will function. But for a moment I'm sitting in front of colorful square on the screen for 10 minutes. I'm newbie in NetBSD, but I have a feeling, that it was stopped for some reason.
-"""]]
--- wikisrc/ports/evbarm/raspberry_pi/comment_8_abec5615a4422a671e582740e4003cba._comment	2018-11-06 12:41:35.000000000 +0000
+++ /dev/null	2018-11-06 12:41:04.000000000 +0000
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/kHl_8WASy82MDC_5T.KtxP08kg--#034a2"
- nickname="George"
- subject="Thanks "
- date="2015-08-15T07:16:05Z"
- content="""
-Thanks for all the great work and for updating your instructions to reflect the new RPI2 images. Which by the way are awesome and right on par now with what the top competition has, in other words *dora has nothing us now with regards to tuning with gcc on this arch.
-
-Last week I took the armv7 gzimg and added the new RPI2 kernel from another snapshot. Wow it worked, and I felt pretty special until the next time I looked 5 minutes later...and I saw I had just took the long route to reproduce what was already done in the new armv7 rpi2 images. LOL.
-
-
-On a site note. Please consider updating the \"Installation\" section example to clarify HEAD/Current images vs Stable. If it's important.
-
-Currently it reads:
-
-\"The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201508062150Z/evbarm-earmv7hf/binary/gzimg/)\"
-
-I would change the \"netbsd-7\" to \"HEAD\" as below, if I'm understanding correctly.
-
-\"The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201508142040Z/evbarm-earmv7hf/binary/gzimg/)\"
-
-
-NetBSD 4 Ever!
-
-
-"""]]

raspberry_pi: explain SD card structure better
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -r1.85 -r1.86
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 02:38:43 -0000	1.85
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 03:13:59 -0000	1.86
@@ -55,11 +55,10 @@
 
 ## SD card structure
 
-The Raspberry Pi looks for firmware and kernel.img on the first FAT32 partition of the uSD card.  A separate kernel (kernel7.img) is used on RPI2 and RPI3.
+The Raspberry Pi looks for firmware and kernel.img on the first FAT32 MBR partition of the uSD card.  A separate kernel (kernel7.img) is used on RPI2 and RPI3.
+The NetBSD kernel will then find NetBSD MBR partition and within that the root disklabel partition, and use that FFS partition as the root filesystem.
 
-The NetBSD kernel will then use the FFS partition as the root filesystem.
-
-A 2 GB card is the smallest workable size.  The NetBSD filesystem will be expanded to fit.
+A 2 GB card is the smallest workable size, and the installation image will fit.  After the first boot, the system resizes the NetBSD root partition to fill the card.  Note that swap is after /boot and before /, and not contained in the NetBSD fdisk partition.  However, if you don't try to change the partition structure, this should not cause you any trouble.
 
 ## Choosing a version
 

raspberry_pi: fix up autobuild links and descriptions
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -r1.84 -r1.85
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:52:21 -0000	1.84
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 02:38:43 -0000	1.85
@@ -83,15 +83,14 @@
 
 Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values on the same system; see build.sh.
 
-### NetBSD FTP servers
+### NetBSD autobuild HTTPS/FTP servers
 
-NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
+NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.  The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type.  It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it.  The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided.
 
- - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
- - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2/3.
- - The old stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
- - The stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
- - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
+ - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that 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, but is also faster than rpi.img.
+
+An example URL, arguably the standard approach for beginners, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/
 
 ## Preparing a uSD card
 

typo
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -r1.83 -r1.84
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:51:49 -0000	1.83
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:52:21 -0000	1.84
@@ -75,7 +75,7 @@
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is eequal to the second in effect, for RPI2/3.
+Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is equal to the second in effect, for RPI2/3.
 
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release

raspberry_pi: adjust wording
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -r1.82 -r1.83
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:45:14 -0000	1.82
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:51:49 -0000	1.83
@@ -75,7 +75,7 @@
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH".  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line is an example (equal to the second in effect, for RPI2/33).
+Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is eequal to the second in effect, for RPI2/3.
 
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release

raspberry_pi: Adjust wording (minor)
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -r1.81 -r1.82
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:42:03 -0000	1.81
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:45:14 -0000	1.82
@@ -75,7 +75,7 @@
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH".  build.sh supports aliases that can be passed a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line is an example (equal to the second in effect).
+Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH".  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line is an example (equal to the second in effect, for RPI2/33).
 
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release

raspberry_pi: Clarify build.sh usage
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 23:20:06 -0000	1.80
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	6 Nov 2018 01:42:03 -0000	1.81
@@ -43,8 +43,10 @@
 # CPU types
 
  - Raspberry Pi 1 uses "earmv6hf".
+ - Raspberry Pi 0 uses "\todo".
  - Raspberry Pi 2 uses "earmv7hf".
  - Raspberry Pi 3 uses "earmv7hf".
+ - Raspberry Pi 0W uses "\todo".
 
 Note that one can run earmv6hf code on the 2 and 3.  See also
 [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
@@ -73,11 +75,13 @@
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.  Pick a CPU type alias and pass it to build.sh with -m.  Examples (the first two are equivalent):
+Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH".  build.sh supports aliases that can be passed a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line is an example (equal to the second in effect).
 
- - ./build.sh -m earmv6hf -u release
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release
+ - ./build.sh -m earmv7hf-el -u release
+
+Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values on the same system; see build.sh.
 
 ### NetBSD FTP servers
 

raspberry_pi: adjust boot wording
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 23:13:40 -0000	1.79
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 23:20:06 -0000	1.80
@@ -136,8 +136,7 @@
 
 ## vcgencmd
 
-The program vcgencmd can be found in pkgsrc/misc/raspberrypi-userland.
-
+The program vcgencmd, referenced in the boot section,  can be found in pkgsrc/misc/raspberrypi-userland.
 
 ## Updating the kernel
 
@@ -168,8 +167,8 @@
 
 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.
 
-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.   \todo Explain if this has been observed to work.
-\todo 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.
+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.
 

raspberry_pi: fix links
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 23:09:40 -0000	1.78
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 23:13:40 -0000	1.79
@@ -160,7 +160,7 @@
 
 ## 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.
+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.
 
@@ -169,7 +169,7 @@
 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.
 
 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.   \todo Explain if this has been observed to work.
-\todo 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 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 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.
 

raspberry_pi: improve links, reference vcgencmd
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -r1.77 -r1.78
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 14:35:31 -0000	1.77
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 23:09:40 -0000	1.78
@@ -134,6 +134,11 @@
 
 # Maintaining a system
 
+## vcgencmd
+
+The program vcgencmd can be found in pkgsrc/misc/raspberrypi-userland.
+
+
 ## Updating the kernel
 
  - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
@@ -155,7 +160,7 @@
 
 ## 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.
+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.
 
@@ -163,9 +168,8 @@
 
 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.
 
-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 be configured via fdisk because the hardware's first-stage boot does not have GPT support.   \todo Explain if this has been observed to work.
-\todo Explain if the [[procedure to program USB host boot mode|https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md]] can function under NetBSD; the examples on the web use Raspbian.
-\todo Explain if there is any way to run vcgencmd on NetBSD.
+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.   \todo Explain if this has been observed to work.
+\todo 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 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.
 

raspberry_pi: fix up fdisk/swap discussion
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 14:28:28 -0000	1.76
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 14:35:31 -0000	1.77
@@ -159,9 +159,9 @@
 
 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.
 
-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 /, but this arrangement permits growing / on first boot, for the typical case where a larger uSD is used.
+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.
 
-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 greateer space, part of the point is to avoid writing to the uSD card.
+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.
 
 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 be configured via fdisk because the hardware's first-stage boot does not have GPT support.   \todo Explain if this has been observed to work.
 \todo Explain if the [[procedure to program USB host boot mode|https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md]] can function under NetBSD; the examples on the web use Raspbian.

raspberry_pi: fix/extend booting discussion
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -r1.75 -r1.76
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 14:19:58 -0000	1.75
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 14:28:28 -0000	1.76
@@ -163,12 +163,12 @@
 
 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 greateer space, part of the point is to avoid writing to the uSD card.
 
-A third approach is to configure USB host booting (default off except on Pi 3+) see the upstream documentation) and have the boot partition also on the external device.  In this case the external device must be configured via fdisk because the hardware's first-stage boot does not have GPT support.   \todo Explain if this has been observed to work.
+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 be configured via fdisk because the hardware's first-stage boot does not have GPT support.   \todo Explain if this has been observed to work.
+\todo Explain if the [[procedure to program USB host boot mode|https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md]] can function under NetBSD; the examples on the web use Raspbian.
+\todo Explain if there is any way to run vcgencmd on NetBSD.
 
 \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.
 
-\todo Explain if the procedure to program USB host boot mode can function under NetBSD; the examples on the web use Raspbian.
-
 # 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.

raspberry_pi: add section on booting
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 13:49:05 -0000	1.74
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 14:19:58 -0000	1.75
@@ -153,9 +153,25 @@
 
 TODO: Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain any particular cautions.
 
+## 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.
+
+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.
+
+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 /, but this arrangement permits growing / on first boot, for the typical case where a larger uSD is used.
+
+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 greateer space, part of the point is to avoid writing to the uSD card.
+
+A third approach is to configure USB host booting (default off except on Pi 3+) see the upstream documentation) and have the boot partition also on the external device.  In this case the external device must be configured via fdisk because the hardware's first-stage boot does not have GPT support.   \todo Explain if this has been observed to work.
+
+\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.
+
+\todo Explain if the procedure to program USB host boot mode can function under NetBSD; the examples on the web use Raspbian.
+
 # Wireless Networking
 
-  Note that the built-in WiFi in the RPI3 is not yet supported.
+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 -

raspberry_pi: clarify what works
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -r1.73 -r1.74
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:49:15 -0000	1.73
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 13:49:05 -0000	1.74
@@ -14,40 +14,40 @@
 
 ## NetBSD 7 and NetBSD 8
 
- - RaspberryPi 1, and 2 (including SMP)
- - Raspberry Pi 3 (excluding WiFi and bluetooth)
- - multi-user boot with root on SD card
+ - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth)
+ - multiple processors on 2/3
+ - 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)
+ - X11 via HDMI
+ - GPU (VCHIQ) - 3D and video decode. man page missing.
+ - USB host controller - dwctwo(4) and most devices work
+ - USB Ethernet - usmsc(4)
  - DMA controller driver and sdhc(4) support
+ - RNG
  - Audio: works. man page missing.
- - I²C: works, could use enhancements, man page
  - GPIO
- - RNG
+ - I²C: works, could use enhancements, man page
  - SPI: could use enhancements, man page
- - GPU (VCHIQ) - 3D and video decode. man page missing.
- - USB (host) - dwctwo(4)
- - USB Ethernet - usmsc(4)
- - X windows.
 
 ## NetBSD current
 
- - Raspberry Pi 3 bluetooth
+ - Raspberry Pi 3 builtin bluetooth
  - Raspberry Pi 3 new SD host controller driver
 
 ## What needs work
 
  - USB (host); isochronous transfers.
- - WiFi
+ - Raspberry Pi 3 builtin WiFi
 
 # CPU types
 
-Note that one can also use code for earlier models on later models.
-
  - Raspberry Pi 1 uses "earmv6hf".
  - Raspberry Pi 2 uses "earmv7hf".
  - Raspberry Pi 3 uses "earmv7hf".
 
-See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
+Note that one can run earmv6hf code on the 2 and 3.  See also
+[[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
 
 # Installation
 
@@ -132,6 +132,8 @@
 
  - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
 
+# Maintaining a system
+
 ## Updating the kernel
 
  - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.

raspberry_pi: Add placeholder for user updates of firmware
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -r1.72 -r1.73
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:40:39 -0000	1.72
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:49:15 -0000	1.73
@@ -145,6 +145,12 @@
  - Depending on your hardware version, copy this either to /boot/kernel.img (First generation Pi, Pi Zero hardware) or to /boot/kernel7.img (Pi 2, Pi 3 hardware)
  - reboot
 
+## Updating the firmware
+
+A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers.  This section is about updating a system's firmware from the firmware in a version of NetBSD.
+
+TODO: Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec).  Explain any particular cautions.
+
 # Wireless Networking
 
   Note that the built-in WiFi in the RPI3 is not yet supported.

raspberry_pi: clarify firmware update developer notes
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:33:39 -0000	1.71
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:40:39 -0000	1.72
@@ -195,22 +195,21 @@
 
 These notes are for people working on improvements to RPI support in NetBSD.
 
-## Updating the firmware
+## Updating the firmware version in the NetBSD sources
 
-You probably don't want to do this. Firmware updates can break things,
-and the latest firmware that's been tested is already included in the
-NetBSD build you installed.
+(Note that trying new firmware may result in a non-bootable system, so
+be prepared to recover the bootable media with another system.)
 
-If you're feeling adventurous (or are the port maintainer), here's what
-to test whenever you try new firmware:
+Upstream firmware releases are
+[on GitHub](https://github.com/raspberrypi/firmware/releases).
+Copy all files except `kernel*.img` into `/boot` and reboot.
+
+New firmware should pass all of the following tests before being committed to NetBSD.
 
 - Audio
 - OMXPlayer (and [[!template id=man name="vchiq"]])
 - Serial/framebuffer console
 - CPU frequency scaling
 
-That goes for all of `rpi[0123]`.
+Tests shoudl be run on all of `rpi[0123]`.
 
-Upstream firmware releases are
-[on GitHub](https://github.com/raspberrypi/firmware/releases).
-Copy all files except `kernel*.img` into `/boot` and reboot.

raspberry_pi: add 64-bit ref, merge old netbsd-7 info, update release
recommendations
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:31:15 -0000	1.70
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:33:39 -0000	1.71
@@ -61,7 +61,7 @@
 
 ## Choosing a version
 
-First, decide if you want to install a formal release (7.1), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  Note that 7.1 predates Raspberry Pi 3 support.  For people who don't know how to choose among those, netbsd-8 is probably best.
+First, decide if you want to install a formal release (7.2 or 8.0), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  For people who don't know how to choose among those, 8.0 or netbsd-8 is probably best.
 
 See also "ebijun's image", below, which is NetBSD-current and includes packages.
 
@@ -84,9 +84,9 @@
 NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
 
  - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
- - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2.
- - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
- - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
+ - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2/3.
+ - The old stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
+ - The stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
  - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
 
 ## Preparing a uSD card

raspberry_pi: add 64-bit ref, merge old netbsd-7 info
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Apr 2018 13:27:58 -0000	1.69
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Oct 2018 01:31:15 -0000	1.70
@@ -2,7 +2,7 @@
 
 This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
 
-Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017.
+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.)
 
 [[images/raspberrypi.jpg]]
 
@@ -12,9 +12,10 @@
 
 # What works (and what doesn't yet)
 
-## NetBSD 7 before July, 2017
+## NetBSD 7 and NetBSD 8
 
  - RaspberryPi 1, and 2 (including SMP)
+ - Raspberry Pi 3 (excluding WiFi and bluetooth)
  - multi-user boot with root on SD card
  - serial or graphics console (with EDID query / parsing)
  - DMA controller driver and sdhc(4) support
@@ -28,10 +29,6 @@
  - USB Ethernet - usmsc(4)
  - X windows.
 
-## NetBSD 7 after July, 2017 and NetBSD 8
-
- - Raspberry Pi 3 (excluding WiFi and bluetooth)
-
 ## NetBSD current
 
  - Raspberry Pi 3 bluetooth
@@ -41,7 +38,6 @@
 
  - USB (host); isochronous transfers.
  - WiFi
- - Raspberry Pi 3 in 64-bit mode.  (Note that this will be provided by the evbarm64 port, rather than evbarm.)
 
 # CPU types
 
@@ -51,6 +47,8 @@
  - Raspberry Pi 2 uses "earmv7hf".
  - Raspberry Pi 3 uses "earmv7hf".
 
+See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
+
 # Installation
 
 ## SD card structure

Add xref to aarch64
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/ports/evbarm.mdwn	26 Oct 2018 07:00:09 -0000	1.49
+++ wikisrc/ports/evbarm.mdwn	30 Oct 2018 01:23:09 -0000	1.50
@@ -35,6 +35,9 @@
 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]].
+
 ### Kernels and userland
 
 The evbarm userland can be used on any system that can run code of the

Note that acorn26 is retired and since when.
Index: wikisrc/ports/acorn26.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn26.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/acorn26.mdwn	19 Jul 2018 10:15:05 -0000	1.15
+++ wikisrc/ports/acorn26.mdwn	26 Oct 2018 21:22:36 -0000	1.16
@@ -1,16 +1,18 @@
 [[!template id=port
 port="acorn26"
 cur_rel="8.0"
-future_rel="9.0"
 pkg_rel="6.1"
 changes_cur="8.0"
-changes_future="9.0"
 thumbnail="http://www.netbsd.org/images/ports/arm26/arch310.gif"
 about="""
-NetBSD/acorn26 is the port of NetBSD to ARMv2 and ARMv2a machines, primarily the
+NetBSD/acorn26 was the port of NetBSD to ARMv2 and ARMv2a machines, primarily the
 Acorn Archimedes, A-series and R-series systems. These systems pre-date those
 supported by NetBSD/acorn32 and use an earlier, incompatible version of the ARM
 architecture.
+
+The port was removed in January 24 2018, and the last release was NetBSD 8.0.
+It was likely dysfunctional in this release.
+
 """
 supported_hardware="""
 ###Supported System Models

Tiny capitalization adjustments.
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/aarch64.mdwn	26 Oct 2018 21:16:21 -0000	1.2
+++ wikisrc/ports/aarch64.mdwn	26 Oct 2018 21:21:56 -0000	1.3
@@ -13,7 +13,7 @@
 on April 1st, 2018.
 
 The original work to do this port was done by Ryo Shimizu, Tohru Nishimura,
-Nick Hudson, Jared D. Mcneill, and Matt Thomas.
+Nick Hudson, Jared D. McNeill, and Matt Thomas.
 
 The port is fully functional. It has been tested on single-CPU and
 multiprocessor configurations, including big.LITTLE asymmetric multiprocessing.

link to aarch64 port page
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/ports.mdwn	26 Oct 2018 21:07:34 -0000	1.17
+++ wikisrc/ports.mdwn	26 Oct 2018 21:19:13 -0000	1.18
@@ -20,7 +20,7 @@
 
 [[!table data="""
 Port		|CPU		|Machines						|Latest Release
-aarch64		|aarch64	|64-bit ARM CPUs					|Not yet released
+[[aarch64]]	|aarch64	|64-bit ARM CPUs					|Not yet released
 [[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[8.0](http://www.netbsd.org/releases/formal-8/)
 [[evbarm]]	|arm		|ARM evaluation boards					|[8.0](http://www.netbsd.org/releases/formal-8/)
 [[evbmips]]	|mips		|MIPS-based evaluation boards				|[8.0](http://www.netbsd.org/releases/formal-8/)
@@ -122,7 +122,7 @@
 
 [[!table data="""
 CPU		|Tier(s)	|Ports(s)
-aarch64		|I		|aarch64
+aarch64		|I		|[[aarch64]]
 alpha		|II		|[[alpha]]
 arm		|I, II		|[[acorn32]] [[cats]] [[epoc32]] [[evbarm]] [[hpcarm]] [[iyonix]] [[netwinder]] [[shark]] [[zaurus]]
 hppa		|II		|[[hppa]]

More amd64->aarch64
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/aarch64.mdwn	26 Oct 2018 21:15:07 -0000	1.1
+++ wikisrc/ports/aarch64.mdwn	26 Oct 2018 21:16:21 -0000	1.2
@@ -1,5 +1,5 @@
 [[!template id=port
-port="amd64"
+port="aarch64"
 future_rel="9.0"
 changes_future="9.0"
 about="""

add aarch64 port page.
I hope not to offend anyone with the listing of names, I used ryo's
announcement on port-arm.
Members: 
	ports/aarch64.mdwn:INITIAL->1.1 

--- /dev/null	2018-10-26 21:15:01.000000000 +0000
+++ wikisrc/ports/aarch64.mdwn	2018-10-26 21:15:20.000000000 +0000
@@ -0,0 +1,25 @@
+[[!template id=port
+port="amd64"
+future_rel="9.0"
+changes_future="9.0"
+about="""
+NetBSD/aarch64 is a port to ARM's 64-bit CPUs and other compatible
+machines.
+
+Running 32-bit NetBSD/arm EABI binaries is supported as well; see
+[[!template id=man name="compat_netbsd32" section="8"]].
+
+The port was first committed to the NetBSD source tree as NetBSD/aarch64
+on April 1st, 2018.
+
+The original work to do this port was done by Ryo Shimizu, Tohru Nishimura,
+Nick Hudson, Jared D. Mcneill, and Matt Thomas.
+
+The port is fully functional. It has been tested on single-CPU and
+multiprocessor configurations, including big.LITTLE asymmetric multiprocessing.
+
+It is not yet available in a release, and will be available in NetBSD 9.0.
+"""
+
+]]
+[[!tag tier1port]]

List aarch64, although it is not released yet and there's no port page.
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports.mdwn	19 Jul 2018 10:06:46 -0000	1.16
+++ wikisrc/ports.mdwn	26 Oct 2018 21:07:34 -0000	1.17
@@ -20,6 +20,7 @@
 
 [[!table data="""
 Port		|CPU		|Machines						|Latest Release
+aarch64		|aarch64	|64-bit ARM CPUs					|Not yet released
 [[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[8.0](http://www.netbsd.org/releases/formal-8/)
 [[evbarm]]	|arm		|ARM evaluation boards					|[8.0](http://www.netbsd.org/releases/formal-8/)
 [[evbmips]]	|mips		|MIPS-based evaluation boards				|[8.0](http://www.netbsd.org/releases/formal-8/)
@@ -106,12 +107,7 @@
 * Port will be bumped up to organic when it is shown to be working.
 * If the port is not reported fixed within the next 6-12 months, it will be moved to the Attic.
 
-Currently there is 1 port with Tier III status. It is:
-
-[[!table data="""
-Port		|CPU		|Machines
-[[acorn26]]	|arm		|Acorn Archimedes, A-series and R-series systems
-"""]]
+Currently there are no port with Tier III status.
 
 
 <hr>
@@ -126,8 +122,9 @@
 
 [[!table data="""
 CPU		|Tier(s)	|Ports(s)
+aarch64		|I		|aarch64
 alpha		|II		|[[alpha]]
-arm		|I, II, III	|[[acorn26]] [[acorn32]] [[cats]] [[epoc32]] [[evbarm]] [[hpcarm]] [[iyonix]] [[netwinder]] [[shark]] [[zaurus]]
+arm		|I, II		|[[acorn32]] [[cats]] [[epoc32]] [[evbarm]] [[hpcarm]] [[iyonix]] [[netwinder]] [[shark]] [[zaurus]]
 hppa		|II		|[[hppa]]
 i386		|I		|[[i386]] [[xen]]
 m68010		|II		|[[sun2]]

Remove no longer present {arm,armeb} port_var.
Problem noticed by <prlw1>, thanks!
Members: 
	ports/evbarm.mdwn:1.48->1.49 

Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/ports/evbarm.mdwn	19 Jul 2018 10:15:05 -0000	1.48
+++ wikisrc/ports/evbarm.mdwn	26 Oct 2018 07:00:09 -0000	1.49
@@ -1,14 +1,12 @@
 [[!template id=port
 port="evbarm"
 port_alt="arm"
-port_var1="arm"
-port_var2="armeb"
-port_var3="earm"
-port_var4="earmeb"
-port_var5="earmv6hf"
-port_var6="earmv7hf"
-port_var7="earmv7hfeb"
-port_var_install_notes="evbarm-arm"
+port_var1="earm"
+port_var2="earmeb"
+port_var3="earmv6hf"
+port_var4="earmv7hf"
+port_var5="earmv7hfeb"
+port_var_install_notes="evbarm-earm"
 cur_rel="8.0"
 future_rel="9.0"
 changes_cur="8.0"

Add FOSDEM 2019
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- wikisrc/events.mdwn	21 Oct 2018 21:35:16 -0000	1.69
+++ wikisrc/events.mdwn	25 Oct 2018 17:34:50 -0000	1.70
@@ -13,6 +13,24 @@
 Future Events
 -------------
 
+### `Feb 2019` - FOSDEM 2019 Brussels, Belgium
+
+*February 2 - 3, 2019, ULB Solbosch Campus, Brussels, Belgium*
+
+[FOSDEM](https://fosdem.org/2019/) is a
+free event for software developers to meet, share ideas
+and collaborate. Every year, thousands of developers of
+free and open source software from all over the world gather
+at the event in Brussels.
+
+There is a special developer's room reserved for BSD licensed
+operating systems and their talks.
+
+Please see
+[this announcement](https://mail-index.NetBSD.org/netbsd-advocacy/2018/10/24/msg000787.html)
+for details.
+
+
 ### `Mar 2019` - AsiaBSDCon 2019, Tokyo, Japan
 
 *March 21 - 24, Tokyo University of Science, Tokyo, Japan*

belatedly mark one PR as fixed
Index: wikisrc/releng/netbsd8.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd8.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/releng/netbsd8.mdwn	22 May 2018 18:24:49 -0000	1.51
+++ wikisrc/releng/netbsd8.mdwn	25 Oct 2018 15:58:33 -0000	1.52
@@ -21,7 +21,7 @@
 
 * [[!template id=pr number=53017]]: Kernel panics every now and then with "fpusave_lwp: did not" message
 
-* [[!template id=pr number=53143]]: NetBSD 8 panic related to procfs (unclear?)
+* ~~[[!template id=pr number=53143]]: NetBSD 8 panic related to procfs~~ (done)
 
 * [[!template id=pr number=53155]]: Wedge after <12h uptime when >2 bnx network interfaces in use /!\
 

add/update
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/releng/netbsd9.mdwn	24 Oct 2018 07:00:09 -0000	1.14
+++ wikisrc/releng/netbsd9.mdwn	25 Oct 2018 15:53:46 -0000	1.15
@@ -32,8 +32,13 @@
 * gcc 8+ from a sanitizers point of view
 * arm: GENERIC kernel config for armv7 boards.
 * arm64: Support for servers following SBSA/SBBR standards
-* updated graphics drivers.
-  - [Almost ready for merge](https://github.com/riastradh/netbsd-src/tree/riastradh-drm), only nouveau blocking changes
+* ~~~updated graphics drivers~~~ (done)
+  - investigate nouveau?
+* PVHVM and PVH
+* ARM64 ACPI
 
+## Nice to have, but likely won't be finished on time
+
+* merge pgoyette-compat
 
 ...

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/releng/netbsd9.mdwn	24 Oct 2018 06:59:27 -0000	1.13
+++ wikisrc/releng/netbsd9.mdwn	24 Oct 2018 07:00:09 -0000	1.14
@@ -11,7 +11,7 @@
 * ATA/NCQ
    - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
    - ~~[[!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=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)

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/releng/netbsd9.mdwn	17 Oct 2018 05:29:43 -0000	1.12
+++ wikisrc/releng/netbsd9.mdwn	24 Oct 2018 06:59:27 -0000	1.13
@@ -11,7 +11,7 @@
 * ATA/NCQ
    - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
    - ~~[[!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
+   - --[[!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)

Remove (spammish) comment
--- wikisrc/tutorials/how_to_use_wpa_supplicant/comment_2_ab04f89f73398d3346a96d1f63be71f8._comment	2018-10-23 19:16:57.000000000 +0000
+++ /dev/null	2018-10-23 19:16:04.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/TKRrGWZqn_MrRssOP4tOGSqPDsxaQuCUrw6XtSI8yFBXNCBJcsSonLdQ635IQu4H3Ad6NJo-#8a016"
- nickname="iPhone Customer"
- subject="Apple application issue "
- date="2018-10-23T07:34:01Z"
- content="""
-I have an issue when I going to download the application on my iPhone and install this its give me an error message whereas I already visit a consulting team by [Apple Application Support](https://www.ipadsupportnumber.com/blog/fix-apple-application-support-error-2/) but I am still facing a problem if anyone has any idea then please suggest me.
-"""]]

define a WRKDIR in mk.conf.frag, see pkg/52413
Index: wikisrc/tutorials/pkgsrc/pbulk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/pbulk.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/tutorials/pkgsrc/pbulk.mdwn	25 Jul 2017 23:27:53 -0000	1.14
+++ wikisrc/tutorials/pkgsrc/pbulk.mdwn	23 Oct 2018 12:19:51 -0000	1.15
@@ -78,6 +78,8 @@
 
 	PKG_DEVELOPER?=         yes
 
+	WRKDIR=                 /tmp/work
+
 	# site specific changes
 
 	PKG_OPTIONS.irssi=      perl inet6

Added a comment: Apple application issue
--- /dev/null	2018-10-23 07:34:05.000000000 +0000
+++ wikisrc/tutorials/how_to_use_wpa_supplicant/comment_2_ab04f89f73398d3346a96d1f63be71f8._comment	2018-10-23 07:34:20.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/TKRrGWZqn_MrRssOP4tOGSqPDsxaQuCUrw6XtSI8yFBXNCBJcsSonLdQ635IQu4H3Ad6NJo-#8a016"
+ nickname="iPhone Customer"
+ subject="Apple application issue "
+ date="2018-10-23T07:34:01Z"
+ content="""
+I have an issue when I going to download the application on my iPhone and install this its give me an error message whereas I already visit a consulting team by [Apple Application Support](https://www.ipadsupportnumber.com/blog/fix-apple-application-support-error-2/) but I am still facing a problem if anyone has any idea then please suggest me.
+"""]]

Move MeetBSD to past events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- wikisrc/events.mdwn	25 Sep 2018 12:17:31 -0000	1.68
+++ wikisrc/events.mdwn	21 Oct 2018 21:35:16 -0000	1.69
@@ -13,16 +13,6 @@
 Future Events
 -------------
 
-### `Oct 2018` - MeetBSDCA 2018, Santa Clara, US
-
-*October 19 - 20, 2018, Intel Santa Clara Campus, California, US*
-
-[MeetBSD California](https://www.meetbsd.com/) is a biennial BSD
-Unix conference that takes place in Silicon Valley. The first
-MeetBSD California took place in 2008 and in 2018 it will take
-place at the Intel Santa Clara Campus.
-
-
 ### `Mar 2019` - AsiaBSDCon 2019, Tokyo, Japan
 
 *March 21 - 24, Tokyo University of Science, Tokyo, Japan*
@@ -40,6 +30,16 @@
 Past Events
 -----------
 
+### `Oct 2018` - MeetBSDCA 2018, Santa Clara, US
+
+*October 19 - 20, 2018, Intel Santa Clara Campus, California, US*
+
+[MeetBSD California](https://www.meetbsd.com/) is a biennial BSD
+Unix conference that takes place in Silicon Valley. The first
+MeetBSD California took place in 2008 and in 2018 it will take
+place at the Intel Santa Clara Campus.
+
+
 ### `Sep 2018` - EuroBSDCon 2018, Bucharest, Romania
 
 *September 20 - 23, 2018, University Politehnica of Bucharest, Romania*

Add a few things.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/releng/netbsd9.mdwn	25 Aug 2018 00:46:15 -0000	1.11
+++ wikisrc/releng/netbsd9.mdwn	17 Oct 2018 05:29:43 -0000	1.12
@@ -10,7 +10,7 @@
    - TODO: docs, what features to add to NPF ...
 * ATA/NCQ
    - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
-   - ~~[[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]~~
+   - ~~[[!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
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
@@ -18,11 +18,14 @@
 * XEN AVX working
    - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
 * ZFS
-* ~~~Kernel Address Sanitizer~~~
+* ~~~kASan for amd64~~~ (done)
+* kASan for aarch64
 * 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
 
 ## Nice to have
 

Fix some spello.
Reported by graff on #NetBSD@Freenode.
Members: 
	examples/netbsd_assembly.mdwn:1.2->1.3 

Index: wikisrc/examples/netbsd_assembly.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/examples/netbsd_assembly.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/examples/netbsd_assembly.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/examples/netbsd_assembly.mdwn	13 Oct 2018 08:35:49 -0000	1.3
@@ -27,7 +27,7 @@
 
 ##   nasm 
 
-NASM (the Netwide Assembler) is a x86 assembler that uses the Intel syntax. It is easily available via [devel/nasm](http://pkgsrc.se/devel/nasm#main). 
+NASM (the Netwide Assembler) is an x86 assembler that uses the Intel syntax. It is easily available via [devel/nasm](http://pkgsrc.se/devel/nasm#main). 
 
 You can also use [devel/yasm](http://pkgsrc.se/devel/yasm#main) with [devel/nasm](http://pkgsrc.se/devel/nasm#main) syntax. 
 
@@ -69,7 +69,7 @@
 
 ###   How to compile and link 
 
-To use the above codes you need to compile and then link them: 
+To use the above code you need to compile and then link it: 
     
     $ nasm -f elf hello.asm
     $ ld -o hello hello.o
@@ -81,7 +81,7 @@
 
 _the portable GNU assembler_
 
-It uses AT&T syntax and designed after the 4.2BSD assembler. You can use it on many CPU architectures. 
+It uses AT&T syntax and is designed after the 4.2BSD assembler. You can use it on many CPU architectures. 
 
 Example: 
     

Sync with global.css -r1.75 on htdocs
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/global.css	19 Aug 2018 16:34:37 -0000	1.9
+++ wikisrc/global.css	5 Oct 2018 15:26:22 -0000	1.10
@@ -1,4 +1,4 @@
-/* $NetBSD: global.css,v 1.9 2018/08/19 16:34:37 maya Exp $ */
+/* $NetBSD: global.css,v 1.10 2018/10/05 15:26:22 leot Exp $ */
 
 /* ##### Common Styles ##### */
 
@@ -366,7 +366,6 @@
 .more {
   margin: 0;
   padding: 0.5em 0;
-  white-space: nowrap;
 }
 
 .more a, .more li a {
@@ -527,6 +526,7 @@
 
 table td {
 	padding: 3pt;
+	text-justify: none;
 }
 
 .centered {
@@ -765,6 +765,7 @@
        only screen and (-webkit-min-device-pixel-ratio: 2) and (max-width: 800px) {
 	body {
 	  font-size: xx-large;
+	  margin-top: 2em;
 	}
 	#centralHeader {
 	  display: none;
@@ -830,15 +831,14 @@
 	}
 
 	.menuicon {
-	  float: right;
-	  position: absolute;
-	  top: 0.5em;
-	  right: 0.5em;
+	  position: fixed;
+	  width: 100%;
+	  background-color: #f8f8f8;
+	  top: 0;
+	  right: 0;
 	  z-index:200;
-	  margin-top: 0.5em;
 	  display: block;
-	  height: 5em;
-	  width: 2em;
+	  height: 2.5em;
 	  -webkit-transition-duration: 0.5s;
 	  -moz-transition-duration: 0.5s;
 	  -ms-transition-duration: 0.5s;
@@ -860,6 +860,8 @@
 	  position: fixed;
 	  width: 2.5em;
 	  height: 0.5em;
+	  top: 1em;
+	  right: 0.5em;
 	  background-color: #fd6720;
 	  border-radius: 0.2em;
 	  -webkit-transition-property: margin, -webkit-transform;

Add a comment