Recent changes to this wiki:

Add TODO
Index: wikisrc/users/ozaki-r.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/ozaki-r.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/ozaki-r.mdwn	17 Dec 2014 13:02:36 -0000	1.1
+++ wikisrc/users/ozaki-r.mdwn	18 Apr 2015 17:00:55 -0000	1.2
@@ -1,5 +1,33 @@
 Ryota Ozaki (ozaki-r)
 
 ## Work area
-* DTrace for ARM
-* MP-safe networking (Layer 2 and network device drivers)
+* Kernel
+  * DTrace
+  * Networking
+    * Layer 2 and Layer 3
+  * Network device drivers
+* Ports
+  * amd64
+  * evbarm
+
+## TODO
+* MP-safe networking
+* Add ATF tests for networking
+* DTrace
+  * Support more providers
+* Kill kvm(3) users
+  * only netstat?
+* Enlarge ifnet#if_flags
+* Restructure ifnet
+  * http://www.mistimed.com/home/BSDNetworking.pdf
+* Refactore ether_output
+  * http://comments.gmane.org/gmane.os.netbsd.devel.network/13403
+  * Pull out routing lookups from ether_output
+* Aggregate interface packet counting
+  * Counting the number of packets and amount of data at different places is a horrible idea
+* Do bpf_mtap at a common place
+  * Regain it from device drivers
+* Make if_link_state_change softint
+  * It can be called from H/W interrupt context while it does many things including sleep-able operations
+  * PR kern/49793
+* Make netipsec a rump component

- mirror the main website change to move acorn26 to tier III
- why isn't there an easier way to do this, i.e. entities?
Members: 
	ports.mdwn:1.6->1.7 

Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports.mdwn	14 Jan 2014 13:52:42 -0000	1.6
+++ wikisrc/ports.mdwn	18 Apr 2015 14:39:41 -0000	1.7
@@ -44,7 +44,6 @@
 
 [[!table data="""
 Port		|CPU		|Machines
-[[acorn26]]	|arm		|Acorn Archimedes, A-series and R-series systems
 [[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles
 [[algor]]	|mips		|Algorithmics MIPS evaluation boards
 [[alpha]]	|alpha		|Digital Alpha (64-bit)
@@ -107,7 +106,13 @@
 * 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 are no ports with Tier III status.
+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
+"""]]
+
 
 <hr>
 
@@ -122,7 +127,7 @@
 [[!table data="""
 CPU		|Tier(s)	|Ports(s)
 alpha		|II		|[[alpha]]
-arm		|I, II		|[[acorn26]] [[acorn32]] [[cats]] [[epoc32]] [[evbarm]] [[hpcarm]] [[iyonix]] [[netwinder]] [[shark]] [[zaurus]]
+arm		|I, II, III	|[[acorn26]] [[acorn32]] [[cats]] [[epoc32]] [[evbarm]] [[hpcarm]] [[iyonix]] [[netwinder]] [[shark]] [[zaurus]]
 hppa		|II		|[[hp700]]
 i386		|I		|[[i386]] [[xen]]
 m68010		|II		|[[sun2]]

note that this has moved to tier III
Index: wikisrc/ports/acorn26.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn26.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/acorn26.mdwn	6 Oct 2014 21:41:28 -0000	1.5
+++ wikisrc/ports/acorn26.mdwn	18 Apr 2015 14:31:38 -0000	1.6
@@ -47,4 +47,4 @@
 * On-board parallel port (lpt)
 """
 ]]
-[[!tag tier2port]]
+[[!tag tier3port]]

update to reality of the last 5 or so years.. with a little more
Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:38:30 -0000	1.8
+++ wikisrc/ports/sparc64.mdwn	16 Apr 2015 21:22:06 -0000	1.9
@@ -9,7 +9,7 @@
 NetBSD/sparc64 is a NetBSD port to Sun's 64-bit UltraSPARC machines. The first
 binary release for sparc64 was [NetBSD 1.5](http://www.NetBSD.org/releases/formal-1.5/).
 NetBSD/sparc64 supports many systems, including Sbus-based UltraSPARC systems
-and PCI-based UltraSPARC systems using UltraSPARC I, II, IIi, and IIe CPU
+and PCI-based UltraSPARC systems using UltraSPARC I, II, IIi, IIe, III, and IIIi CPU
 types.
 
 NetBSD/sparc64 supports both 32-bit and 64-bit kernels. A 32-bit kernel runs
@@ -31,7 +31,7 @@
 * Ultra 2 family (Ultra 2, Ultra 2 Creator, Ultra 2 Creator 3D, Enterprise 2) 
 * Enterprise (3000, 3500, 4000, 4500, 500x, 5500, 600x, 6500, 10000) 
 
-### PCI-based UltraSPARC II, IIi, or IIe systems 
+### PCI-based UltraSPARC II, IIi, IIe, III or IIIi systems 
 
 * Ultra 5/10 family (Ultra 5, Ultra 10, Enterprise 5, Enterprise 10) 
 * Ultra 30 family (Ultra 30, Netra T 1100) 
@@ -39,10 +39,14 @@
 * Ultra 80 family (Ultra 80, E420R, Netra T 1400 and T 1405) 
 * Ultra 250 family (Enterprise 250 and E250R) 
 * Ultra 450 family (Ultra 450, Enterprise 450, Netra ft 1800) 
-* Blade 100 and 150 
+* SunBlade 100 and 150 
 * SPARCengine CP1400 or SPARCengine CP1500 system boards (Netra T1 (models 100 and 105), CT400, CT800, CT1600) 
 * SPARCengine Ultra AXi family (Netra X1, Fire v100, Fire v120, Netra 120, Netra AC 200, Netra DC 200) 
 * SPARCengine Ultra AXe system board 
+* SunBlade 1000 and 2000
+* SunBlade 1500, 2500 (Red and Silver)
+* Ultra 25 and 45
+* Sun Fire v125, v210, v215, v240, v245, v250, v440, v445, v480
 
 See the [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html) page for a complete list.
 
@@ -64,12 +68,13 @@
 * Most Machine-independent [SBUS cards](http://www.NetBSD.org/support/hardware/sbus.html)
 * Most Machine-independent [PCI cards](http://www.NetBSD.org/support/hardware/pci.html)
 * Most Machine-independent [USB device](http://www.NetBSD.org/support/hardware/usb.html)
+* Lights Out Management
 * FireWire 
 """
 unsupported_hardware="""
-* Systems with an UltraSPARC III CPU 
-* Systems with an UltraSPARC IIIi CPU 
-* Systems with an UltraSPARC IV CPU 
+* Systems with an UltraSPARC IV CPU (unknown; may work)
+* Systems with an UltraSPARC T1-T5 CPU (in-progress)
+* Systems with an Fujitsu SPARC64 CPU (in-progress)
 * Smart card readers 
 """
 additional="""

Added a comment
--- /dev/null	2015-04-16 15:50:00.000000000 +0000
+++ wikisrc/tutorials/how_to_use_wpa_supplicant/comment_1_e0f19af93ecceeab6ea0843071fc84a6._comment	2015-04-16 15:53:29.000000000 +0000
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawl9QXvSj0CybSZbeFgyaRwKIoaGaRsCb6k"
+ nickname="Frank"
+ subject="comment 1"
+ date="2015-04-16T15:52:11Z"
+ content="""
+Determine first what interfaces are available:
+
+    ifconfig -l
+
+Add to /etc/rc.conf:
+
+    dhclient=YES
+    # Do not wait for lease; useful if no network is within reach, so boot will not hang
+    dhclient_flags=\"-nw\"
+    wpa_supplicant=YES
+    # select the appropriate interface (-i) for your wifi card. (i.e. -i wpi0)
+    wpa_supplicant_flags=\"-B -i wpi0 -c /etc/wpa_supplicant.conf\"
+"""]]

Added a comment: firmware update
--- /dev/null	2015-04-15 12:50:00.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_7_7fbf9e5dada4e180566e226e89de346f._comment	2015-04-15 12:59:00.000000000 +0000
@@ -0,0 +1,14 @@
+[[!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
+"""]]

add BeagleBone Black, BeagleBoard, BeagleBoard-xM
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/evbarm.mdwn	29 Mar 2015 21:18:29 -0000	1.18
+++ wikisrc/ports/evbarm.mdwn	15 Apr 2015 12:53:38 -0000	1.19
@@ -84,8 +84,11 @@
  * CompactFlash socket (_eppcic_)
  * USB 1.1 ports (_ohci_)
 
-### BeagleBoard.org **BeagleBone**
-The [[BeagleBone]] is a low-cost credit-card-sized computer from BeagleBoard.
+### BeagleBoard.org **BeagleBoard** and **BeagleBoard-xM**
+The [[BeagleBoard]] is a low-power open-source hardware single-board computer from BeagleBoard.org.
+
+### BeagleBoard.org **BeagleBone** and **BeagleBone Black**
+The [[BeagleBone]] is a low-cost credit-card-sized computer from BeagleBoard.org.
 
 ### Gumstix, Inc. **gumstix**
 

Index: wikisrc/ports/evbarm/beaglebone.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/beaglebone.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/evbarm/beaglebone.mdwn	15 Apr 2015 12:45:16 -0000	1.9
+++ wikisrc/ports/evbarm/beaglebone.mdwn	15 Apr 2015 12:49:39 -0000	1.10
@@ -1,4 +1,4 @@
-[[!meta title="NetBSD/evbarm on BeagleBone"]]
+[[!meta title="NetBSD/evbarm on BeagleBone and BeagleBone Black"]]
 
 [[images/beaglebone.jpg]]
 

add beaglebone black, update supported feature list, new dmesg
Index: wikisrc/ports/evbarm/beaglebone.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/beaglebone.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/evbarm/beaglebone.mdwn	6 Jan 2014 18:11:54 -0000	1.8
+++ wikisrc/ports/evbarm/beaglebone.mdwn	15 Apr 2015 12:45:16 -0000	1.9
@@ -2,19 +2,20 @@
 
 [[images/beaglebone.jpg]]
 
-This page attempts to document and coordinate efforts towards NetBSD on [BeagleBone](http://beagleboard.org/bone).
+This page attempts to document and coordinate efforts towards NetBSD on [BeagleBone](http://beagleboard.org/bone) and [BeagleBone Black](http://beagleboard.org/black).
 
 (BeagleBone [image](http://www.flickr.com/photos/sparkfun/8267577194/) by SparkFun Electronics used under CC-By-2.0 license)
 
 # What works
  - Boots multi-user on [[!template id=man name="ld" section="4"]] @ [[!template id=man name="sdmmc" section="4"]] root and [[!template id=man name="com" section="4"]] console.
  - Ethernet ([[!template id=man name="cpsw" section="4" arch="evbarm"]])
+ - EDMA3 (for [[!template id=man name="sdhc" section="4"]])
+ - USB (host)
+ - I²C
+ - CPU frequency scaling (various speeds between 300MHz and 1GHz)
 
 # What needs work
- - EDMA3 (perhaps at first for [[!template id=man name="sdhc" section="4"]])
- - USB (host)
  - SPI
- - I²C
  - GPIO
  - Framebuffer/graphics with LCD or DVI/HDMI capes
  - Touchscreens on LCD capes
@@ -22,47 +23,71 @@
 
 # Sample dmesg
 [[!template id=filecontent name="dmesg" text="""
-NetBSD 6.99.16 (BEAGLEBONE)
-total memory = 256 MB
-avail memory = 247 MB
+NetBSD 7.99.9 (BEAGLEBONE) #2: Tue Apr 14 20:24:09 ADT 2015
+        Jared@Jared-PC:/cygdrive/d/netbsd/src/sys/arch/evbarm/compile/obj/BEAGLEBONE
+total memory = 512 MB
+avail memory = 503 MB
+sysctl_createv: sysctl_create(machine_arch) returned 17
 timecounter: Timecounters tick every 10.000 msec
-cprng kernel: WARNING insufficient entropy at creation.
 mainbus0 (root)
-cpu0 at mainbus0 core 0: 720 MHz Cortex-A8 r3p2 (Cortex core)
+cpu0 at mainbus0 core 0: 550 MHz Cortex-A8 r3p2 (Cortex V7A core)
 cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
 cpu0: isar: [0]=0x101111 [1]=0x13112111 [2]=0x21232031 [3]=0x11112131, [4]=0x11142, [5]=0
 cpu0: mmfr: [0]=0x1100003 [1]=0x20000000 [2]=0x1202000 [3]=0x211
 cpu0: pfr: [0]=0x1131 [1]=0x11
-cpu0: 32KB/64B 4-way L1 Instruction cache
-cpu0: 32KB/64B 4-way write-back-locking-C L1 Data cache
-cpu0: 256KB/64B 8-way write-through L2 Unified cache
-vfp0 at cpu0: NEON MPE (VFP 3.0+)
+cpu0: 32KB/64B 4-way L1 VIPT Instruction cache
+cpu0: 32KB/64B 4-way write-back-locking-C L1 PIPT Data cache
+cpu0: 256KB/64B 8-way write-through L2 PIPT Unified cache
+vfp0 at cpu0: NEON MPE (VFP 3.0+), rounding, NaN propagation, denormals
+vfp0: mvfr: [0]=0x11110222 [1]=0x11111
 obio0 at mainbus0 base 0x44000000-0x4fffffff: On-Board IO
 omapicu0 at obio0 addr 0x48200000-0x48200fff intrbase 0
 prcm0 at obio0 addr 0x44e00000-0x44e01fff: Power, Reset and Clock Management
-gpmc0 at mainbus0 base 0x50000000-0x50ffffff: General Purpose Memory Controller, rev 6.0
+sitaracm0 at obio0 addr 0x44e10000-0x44e11fff: control module, rev 1.0
+edma0 at obio0 addr 0x49000000-0x490fffff intrbase 12
+gpmc0 at mainbus0 base 0x50000000: General Purpose Memory Controller, rev 6.0
 gpmc0: CS#0 valid, addr 0x08000000, size 256MB
 com0 at obio0 addr 0x44e09000-0x44e09fff intr 72: ns16550a, working fifo
 com0: console
-sdhc0 at obio0 addr 0x48060100-0x48060fff intr 64: SDHC controller
+sdhc0 at obio0 addr 0x48060100-0x48060fff intr 64: SDHC controller (EDMA)
 sdhc0: SD Host Specification 2.0, rev.49
+sdhc0: using DMA transfer
 sdmmc0 at sdhc0 slot 0
+sdhc1 at obio0 addr 0x481d8100-0x481d8fff intr 28: SDHC controller (EDMA)
+sdhc1: SD Host Specification 2.0, rev.49
+sdhc1: using DMA transfer
+sdmmc1 at sdhc1 slot 0
+tiiic0 at obio0 addr 0x44e0b000-0x44e0bfff intr 70: rev 0.11
+iic0 at tiiic0: I2C bus
+seeprom0 at iic0 addr 0x50: AT24Cxx or compatible EEPROM: size 32768
+tps65217pmic0 at iic0 addr 0x24: TPS65217C Power Management Multi-Channel IC (rev 1.2)
+tps65217pmic0: power sources USB max 1300 mA, [AC] max 2500 mA
+tps65217pmic0: [LDO1: 1800 mV] [LDO2: 3300 mV] [LDO3: 1800 mV] [LDO4: 3300 mV] [DCDC1: 1500 mV] [DCDC2: 1325 mV] [DCDC3: 1100 mV]
 omapdmtimer0 at obio0 addr 0x48040000-0x48040fff intr 68: DMTIMER2
 omapdmtimer1 at obio0 addr 0x44e31000-0x44e31fff intr 67: DMTIMER1ms
 omapdmtimer2 at obio0 addr 0x48044000-0x48044fff intr 92: DMTIMER4
 omapwdt32k0 at obio0 addr 0x44e35000-0x44e35fff: rev 0.1
+tiotg0 at obio0 addr 0x47400000-0x47404fff intrbase 17: TI dual-port USB controller: version v1.0.0.13
+motg0 at tiotg0 port 0: 0x4ea20800 version v0.0.0
+motg1 at tiotg0 port 1: 0x4ea20800 version v0.0.0
+motg1: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM
+usb0 at motg1: USB revision 2.0
+cpsw0 at obio0 addr 0x4a100000-0x4a107fff intrbase 40: TI CPSW Ethernet
+cpsw0: Ethernet address 90:59:af:5c:d0:94
+ukphy0 at cpsw0 phy 0: OUI 0x00800f, model 0x000f, rev. 1
+ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 timecounter: Timecounter "dmtimer" frequency 24000000 Hz quality 100
-ld0 at sdmmc0: <0x28:0x4245:31676:0x10::0x0a7>
-ld0: 490 MB, 995 cyl, 16 head, 63 sec, 512 bytes/sect x 1003520 sectors
-ld0: 4-bit width, bus clock 50.000 MHz
-cprng sysctl: WARNING insufficient entropy at creation.
-boot device: <unknown>
-root on ld0f dumps on ld0b
-WARNING: no TOD clock present
-WARNING: using filesystem time
-WARNING: CHECK AND RESET THE DATE!
-init: copying out path `/sbin/init' 11
+uhub0 at usb0: Mentor Graphics MOTG root hub, class 9/0, rev 1.00/1.00, addr 1
+uhub0: 1 port with 1 removable, self powered
+sdmmc0: couldn't enable card: 60
+ld1 at sdmmc1: <0xfe:0x014e:MMC02G:0x00:0x1aee3308:0x000>
+ld1: 1832 MB, 930 cyl, 64 head, 63 sec, 512 bytes/sect x 3751936 sectors
+ld1: 4-bit width, bus clock 52.000 MHz
+boot device: ld1
+root on ld1a dumps on ld1b
+root file system type: ffs
+kern.module.path=/stand/evbarm/7.99.9/modules
 """]]
 
 

removed
--- wikisrc/projects/project/ext3fs/comment_1_69ddea24110385c9beaeed39e462571f._comment	2015-04-14 00:02:24.000000000 +0000
+++ /dev/null	2015-04-14 00:00:00.000000000 +0000
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlLa6Bkv1immtQk3WsGQa8ZPqO2bljJUGk"
- nickname="Manali"
- subject="Is this still an open project?"
- date="2015-04-13T18:28:56Z"
- content="""
-Is this still an open project? Or has someone started weking on this already? Where does one contact for reviews/sunmits el al?
-
-
-
-"""]]

Added a comment: Is this still an open project?
--- /dev/null	2015-04-13 18:32:00.000000000 +0000
+++ wikisrc/projects/project/ext3fs/comment_3_071684da617470582705c908df16a4d6._comment	2015-04-13 18:34:07.000000000 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlLa6Bkv1immtQk3WsGQa8ZPqO2bljJUGk"
+ nickname="Manali"
+ subject="Is this still an open project?"
+ date="2015-04-13T18:32:48Z"
+ content="""
+Is this still an open project? Or has someone started working on this already? Where does one contact for reviews/submits el al?
+
+"""]]

Added a comment: Is this still an open project?
--- /dev/null	2015-04-13 18:30:03.000000000 +0000
+++ wikisrc/projects/project/ext3fs/comment_2_784e473465d7664071469032b8df63a4._comment	2015-04-13 18:31:56.000000000 +0000
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlLa6Bkv1immtQk3WsGQa8ZPqO2bljJUGk"
+ nickname="Manali"
+ subject="Is this still an open project?"
+ date="2015-04-13T18:30:39Z"
+ content="""
+Is this still an open project? Or has someone started working on this already? Where does one contact for reviews/submits el al?
+
+
+
+"""]]

Added a comment: Is this still an open project?
--- /dev/null	2015-04-13 18:30:03.000000000 +0000
+++ wikisrc/projects/project/ext3fs/comment_1_69ddea24110385c9beaeed39e462571f._comment	2015-04-13 18:30:18.000000000 +0000
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlLa6Bkv1immtQk3WsGQa8ZPqO2bljJUGk"
+ nickname="Manali"
+ subject="Is this still an open project?"
+ date="2015-04-13T18:28:56Z"
+ content="""
+Is this still an open project? Or has someone started weking on this already? Where does one contact for reviews/sunmits el al?
+
+
+
+"""]]

Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/evbarm/tegra.mdwn	11 Apr 2015 17:21:30 -0000	1.1
+++ wikisrc/ports/evbarm/tegra.mdwn	11 Apr 2015 17:22:18 -0000	1.2
@@ -13,6 +13,6 @@
 
 # Links
 
-[NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1)
-[Hardware documentation](https://developer.nvidia.com/hardware-design-and-development)
-[Linux For Tegra](https://developer.nvidia.com/linux-tegra)
+- [NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1)
+- [Hardware documentation](https://developer.nvidia.com/hardware-design-and-development)
+- [Linux For Tegra](https://developer.nvidia.com/linux-tegra)

--- /dev/null	2015-04-11 17:20:01.000000000 +0000
+++ wikisrc/ports/evbarm/tegra.mdwn	2015-04-11 17:21:33.000000000 +0000
@@ -0,0 +1,18 @@
+[[!meta title="NetBSD/evbarm on NVIDIA Tegra"]]
+
+**The Tegra port is work in progress**
+
+# Generating a boot script
+
+[[!template  id=programlisting text="""
+$ cat boot.txt
+fatload mmc 1:1 0x90000000 netbsd.ub
+bootm 0x90000000
+$ mkubootimage -A arm -C none -O netbsd -T script -a 0 -n "NetBSD/tegra boot" boot.txt boot.scr
+"""]]
+
+# Links
+
+[NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1)
+[Hardware documentation](https://developer.nvidia.com/hardware-design-and-development)
+[Linux For Tegra](https://developer.nvidia.com/linux-tegra)

Added a comment: Lumina
--- /dev/null	2015-04-08 14:50:00.000000000 +0000
+++ wikisrc/projects/project/desktop-infrastructure/comment_1_c61f4caff341973313ef3915f80de63a._comment	2015-04-08 14:56:09.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlN-bEl-rumc5eN8TeuhJ-PaFhxohDg22k"
+ nickname="J. Lewis"
+ subject="Lumina"
+ date="2015-04-08T14:54:50Z"
+ content="""
+Perhaps it's worth considering the [Lumina](https://github.com/pcbsd/lumina) desktop environment from [PC-BSD](http://www.pcbsd.org/).
+"""]]

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	29 Mar 2015 21:32:29 -0000	1.39
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Apr 2015 10:10:04 -0000	1.40
@@ -27,7 +27,7 @@
 
 	   edit cmdline.txt and remove '"console=fb"'
 
- - Growing the root file-system
+ - Growing the root file-system (**not required with NetBSD -current after 2015-04-07**)
    - 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

Added a comment: Development environment for compiling netbsd for raspberry pi 2
--- /dev/null	2015-04-05 17:50:01.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_6_6a8a5c909e9d832060e5e95a9094d4f4._comment	2015-04-05 17:54:55.000000000 +0000
@@ -0,0 +1,8 @@
+[[!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.
+"""]]

removed
--- wikisrc/ports/evbarm/raspberry_pi/comment_6_64382f6f83c71a0f35165e6f25eb5758._comment	2015-04-05 17:47:04.000000000 +0000
+++ /dev/null	2015-04-05 17:40:00.000000000 +0000
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlLcRxMII5dryjSOMJ_FMeMUJvok7A5GtU"
- nickname="Darshana"
- subject="Development environment for compiling netbsd for raspberry pi 2"
- date="2015-04-05T17:34:24Z"
- content="""
-It seems that netbsd 7.0 has the support for raspberry pi 2.. Can anyone please post where can i get the sources for netbsd 7.0? I am trying to compile netbsd for my new raspberry pi 2 board.  
-
-Thanks
-"""]]

Added a comment: Development environment for compiling netbsd for raspberry pi 2
--- /dev/null	2015-04-05 17:34:16.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_6_64382f6f83c71a0f35165e6f25eb5758._comment	2015-04-05 17:35:43.000000000 +0000
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlLcRxMII5dryjSOMJ_FMeMUJvok7A5GtU"
+ nickname="Darshana"
+ subject="Development environment for compiling netbsd for raspberry pi 2"
+ date="2015-04-05T17:34:24Z"
+ content="""
+It seems that netbsd 7.0 has the support for raspberry pi 2.. Can anyone please post where can i get the sources for netbsd 7.0? I am trying to compile netbsd for my new raspberry pi 2 board.  
+
+Thanks
+"""]]

removed
--- wikisrc/ports/evbarm/raspberry_pi/comment_6_788dd56a019e6f122201b71dde4ac04d._comment	2015-04-05 17:31:13.000000000 +0000
+++ /dev/null	2015-04-05 17:30:00.000000000 +0000
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlLcRxMII5dryjSOMJ_FMeMUJvok7A5GtU"
- nickname="Darshana"
- subject="Development environment for compiling netbsd for raspberry pi 2"
- date="2015-04-05T17:22:09Z"
- content="""
-I see that support for raspberry pi 2 is there in netbsd 7.0. But i do not see the sources available. I am interested in compiling netbsd 7.0 for raspberry pi 2 board. Can someone please post it here?
-
--Alakesh Haloi
-"""]]

Added a comment: Development environment for compiling netbsd for raspberry pi 2
--- /dev/null	2015-04-05 17:20:01.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_6_788dd56a019e6f122201b71dde4ac04d._comment	2015-04-05 17:23:26.000000000 +0000
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlLcRxMII5dryjSOMJ_FMeMUJvok7A5GtU"
+ nickname="Darshana"
+ subject="Development environment for compiling netbsd for raspberry pi 2"
+ date="2015-04-05T17:22:09Z"
+ content="""
+I see that support for raspberry pi 2 is there in netbsd 7.0. But i do not see the sources available. I am interested in compiling netbsd 7.0 for raspberry pi 2 board. Can someone please post it here?
+
+-Alakesh Haloi
+"""]]

document fb.depth
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/evbarm/odroid-c1.mdwn	29 Mar 2015 21:29:58 -0000	1.13
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	3 Apr 2015 20:23:55 -0000	1.14
@@ -131,6 +131,10 @@
 setenv bootcmd "video dev open 1080P; fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 """]]
 
+## 16 or 24 bpp?
+
+ODROID-C1 defaults to 16bpp. If you want to try 24bpp, add **fb.depth=24** to the kernel cmdline options in *boot.ini*. There are some issues with 24bpp mode and Xorg; see <http://gnats.netbsd.org/49812>.
+
 ## Overscan compensation
 
 If you have ODROID-C1 plugged into a TV, the edges of the screen may not be visible. You can scale down the framebuffer console with the **hw.genfb0.scale** sysctl, e.g.:

Updated A80 install notes
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/ports/evbarm/allwinner.mdwn	29 Mar 2015 21:33:24 -0000	1.49
+++ wikisrc/ports/evbarm/allwinner.mdwn	2 Apr 2015 18:36:59 -0000	1.50
@@ -88,22 +88,12 @@
 
 ## A80 based boards
 
-* Cubieboard 4 SDK (lubuntu) U-Boot env:
+* Cubieboard 4 U-Boot for SD card: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/allwinner/a80/cubieboard4-uboot.tgz>
 [[!template  id=programlisting text="""
-baudrate=115200
-boot_normal=fatload mmc 0:1 20007800 uimage;bootm 20007800
-bootcmd=run setargs_cubie boot_normal
-bootdelay=3
-console=ttyS0,115200
-console1=tty1
-init=/init
-loglevel=8
-mmc_root=/dev/mmcblk0p2
-setargs_cubie=setenv bootargs console=${console1} console=${console} root=${mmc_root} loglevel=${loglevel}
-stderr=serial
-stdin=serial
-stdout=serial
+# dd if=u-boot-spl.bin of=/dev/sdd bs=1k seek=8
+# dd if=u-boot-sun9iw1p1.bin of=/dev/sdd bs=1k seek=19096
 """]]
+* First partition needs to be at +20MB offset. Format it as MSDOS, copy 'netbsd.ub' to it as 'uImage'.
 
 # Big (endian) fun
 

removed
--- wikisrc/projects/project/troff/comment_3_0b9ada5ade05088ca10db67c8ae1bafe._comment	2015-03-31 20:26:40.000000000 +0000
+++ /dev/null	2015-03-31 20:20:00.000000000 +0000
@@ -1,57 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
- nickname="Benjamin"
- subject="A book writer needs a Fountain pen. Not a printing press."
- date="2015-03-31T20:20:12Z"
- content="""
-Thoughts from a passers-by:
-
-Let the output formats (we need most!) dictate the requirements of the tool.  
-Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
-Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
-If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
-Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
-
-A writer needs a tool which concentrates his thought. A printing press expands thought.  
-What will the writer do if one gives the writer a printing press?  
-
-Why should the available book formats define the pen of the writer?
-'Content rules format.'  
-
-I see a collection of printing presses. They can do a lot.  
-I read: They don't do the job 'software documentation'.  
-But what does this all have to do with solving the task 'software documentation'?  
-Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
-To me it is:
-
-I. Hierarchy  
-   1. Headings  
-   1. Lists  
-I. Descriptive text
-I. Non-descriptive text (quotes)
-   1. Inline
-   1. Multiline
-I. References  
-   1. Internal
-   1. External
-      1. Author, Title, Date, Location
-      1. URI
-I. Images
-
-Blocks of texts are organised in an hierarchy (a1).  
-Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
-A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
-A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
-I leave it to some higher power whether images (e) are required.  
-The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
-
-That's it.  
-
-'But I need to highlight some description text.' No, you don't.  
-If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
-USE CAPS.  
-o r  s p a c e.  
-O R  B O T H.
-
-You haven't seen anything. Continue your walk.
-"""]]

removed
--- wikisrc/projects/project/troff/comment_4_d2af902400f171479d8fa3babef55ce6._comment	2015-03-31 20:25:53.000000000 +0000
+++ /dev/null	2015-03-31 20:20:00.000000000 +0000
@@ -1,57 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
- nickname="Benjamin"
- subject="A book writer needs a Fountain pen. Not a printing press."
- date="2015-03-31T20:21:40Z"
- content="""
-Thoughts from a passers-by:
-
-Let the output formats (we need most!) dictate the requirements of the tool.  
-Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
-Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
-If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
-Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
-
-A writer needs a tool which concentrates his thought. A printing press expands thought.  
-What will the writer do if one gives the writer a printing press?  
-
-Why should the available book formats define the pen of the writer?
-'Content rules format.'  
-
-I see a collection of printing presses. They can do a lot.  
-I read: They don't do the job 'software documentation'.  
-But what does this all have to do with solving the task 'software documentation'?  
-Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
-To me it is:
-
-I. Hierarchy  
-   1. Headings  
-   1. Lists  
-I. Descriptive text
-I. Non-descriptive text (quotes)
-   1. Inline
-   1. Multiline
-I. References  
-   1. Internal
-   1. External
-      1. Author, Title, Date, Location
-      1. URI
-I. Images
-
-Blocks of texts are organised in an hierarchy (a1).  
-Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
-A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
-A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
-I leave it to some higher power whether images (e) are required.  
-The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
-
-That's it.  
-
-'But I need to highlight some description text.' No, you don't.  
-If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
-USE CAPS.  
-o r  s p a c e.  
-O R  B O T H.
-
-You haven't seen anything. Continue your walk.
-"""]]

removed
--- wikisrc/projects/project/troff/comment_5_158ba9974609ae7b7748da533cf27fcc._comment	2015-03-31 20:25:17.000000000 +0000
+++ /dev/null	2015-03-31 20:20:00.000000000 +0000
@@ -1,57 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
- nickname="Benjamin"
- subject="A book writer needs a Fountain pen. Not a printing press."
- date="2015-03-31T20:23:28Z"
- content="""
-Thoughts from a passers-by:
-
-Let the output formats (we need most!) dictate the requirements of the tool.  
-Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
-Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
-If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
-Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
-
-A writer needs a tool which concentrates his thought. A printing press expands thought.  
-What will the writer do if one gives the writer a printing press?  
-
-Why should the available book formats define the pen of the writer?
-'Content rules format.'  
-
-I see a collection of printing presses. They can do a lot.  
-I read: They don't do the job 'software documentation'.  
-But what does this all have to do with solving the task 'software documentation'?  
-Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
-To me it is:
-
-I. Hierarchy  
-   1. Headings  
-   1. Lists  
-I. Descriptive text
-I. Non-descriptive text (quotes)
-   1. Inline
-   1. Multiline
-I. References  
-   1. Internal
-   1. External
-      1. Author, Title, Date, Location
-      1. URI
-I. Images
-
-Blocks of texts are organised in an hierarchy (a1).  
-Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
-A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
-A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
-I leave it to some higher power whether images (e) are required.  
-The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
-
-That's it.  
-
-'But I need to highlight some description text.' No, you don't.  
-If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
-USE CAPS.  
-o r  s p a c e.  
-O R  B O T H.
-
-You haven't seen anything. Continue your walk.
-"""]]

Added a comment: A book writer needs a Fountain pen. Not a printing press.
--- /dev/null	2015-03-31 20:20:00.000000000 +0000
+++ wikisrc/projects/project/troff/comment_5_158ba9974609ae7b7748da533cf27fcc._comment	2015-03-31 20:24:46.000000000 +0000
@@ -0,0 +1,57 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
+ nickname="Benjamin"
+ subject="A book writer needs a Fountain pen. Not a printing press."
+ date="2015-03-31T20:23:28Z"
+ content="""
+Thoughts from a passers-by:
+
+Let the output formats (we need most!) dictate the requirements of the tool.  
+Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
+Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
+If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
+Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
+
+A writer needs a tool which concentrates his thought. A printing press expands thought.  
+What will the writer do if one gives the writer a printing press?  
+
+Why should the available book formats define the pen of the writer?
+'Content rules format.'  
+
+I see a collection of printing presses. They can do a lot.  
+I read: They don't do the job 'software documentation'.  
+But what does this all have to do with solving the task 'software documentation'?  
+Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
+To me it is:
+
+I. Hierarchy  
+   1. Headings  
+   1. Lists  
+I. Descriptive text
+I. Non-descriptive text (quotes)
+   1. Inline
+   1. Multiline
+I. References  
+   1. Internal
+   1. External
+      1. Author, Title, Date, Location
+      1. URI
+I. Images
+
+Blocks of texts are organised in an hierarchy (a1).  
+Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
+A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
+A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
+I leave it to some higher power whether images (e) are required.  
+The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
+
+That's it.  
+
+'But I need to highlight some description text.' No, you don't.  
+If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
+USE CAPS.  
+o r  s p a c e.  
+O R  B O T H.
+
+You haven't seen anything. Continue your walk.
+"""]]

Added a comment: A book writer needs a Fountain pen. Not a printing press.
--- /dev/null	2015-03-31 20:20:00.000000000 +0000
+++ wikisrc/projects/project/troff/comment_4_d2af902400f171479d8fa3babef55ce6._comment	2015-03-31 20:22:59.000000000 +0000
@@ -0,0 +1,57 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
+ nickname="Benjamin"
+ subject="A book writer needs a Fountain pen. Not a printing press."
+ date="2015-03-31T20:21:40Z"
+ content="""
+Thoughts from a passers-by:
+
+Let the output formats (we need most!) dictate the requirements of the tool.  
+Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
+Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
+If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
+Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
+
+A writer needs a tool which concentrates his thought. A printing press expands thought.  
+What will the writer do if one gives the writer a printing press?  
+
+Why should the available book formats define the pen of the writer?
+'Content rules format.'  
+
+I see a collection of printing presses. They can do a lot.  
+I read: They don't do the job 'software documentation'.  
+But what does this all have to do with solving the task 'software documentation'?  
+Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
+To me it is:
+
+I. Hierarchy  
+   1. Headings  
+   1. Lists  
+I. Descriptive text
+I. Non-descriptive text (quotes)
+   1. Inline
+   1. Multiline
+I. References  
+   1. Internal
+   1. External
+      1. Author, Title, Date, Location
+      1. URI
+I. Images
+
+Blocks of texts are organised in an hierarchy (a1).  
+Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
+A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
+A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
+I leave it to some higher power whether images (e) are required.  
+The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
+
+That's it.  
+
+'But I need to highlight some description text.' No, you don't.  
+If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
+USE CAPS.  
+o r  s p a c e.  
+O R  B O T H.
+
+You haven't seen anything. Continue your walk.
+"""]]

Added a comment: A book writer needs a Fountain pen. Not a printing press.
--- /dev/null	2015-03-31 20:20:00.000000000 +0000
+++ wikisrc/projects/project/troff/comment_3_0b9ada5ade05088ca10db67c8ae1bafe._comment	2015-03-31 20:21:30.000000000 +0000
@@ -0,0 +1,57 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
+ nickname="Benjamin"
+ subject="A book writer needs a Fountain pen. Not a printing press."
+ date="2015-03-31T20:20:12Z"
+ content="""
+Thoughts from a passers-by:
+
+Let the output formats (we need most!) dictate the requirements of the tool.  
+Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
+Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
+If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
+Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
+
+A writer needs a tool which concentrates his thought. A printing press expands thought.  
+What will the writer do if one gives the writer a printing press?  
+
+Why should the available book formats define the pen of the writer?
+'Content rules format.'  
+
+I see a collection of printing presses. They can do a lot.  
+I read: They don't do the job 'software documentation'.  
+But what does this all have to do with solving the task 'software documentation'?  
+Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
+To me it is:
+
+I. Hierarchy  
+   1. Headings  
+   1. Lists  
+I. Descriptive text
+I. Non-descriptive text (quotes)
+   1. Inline
+   1. Multiline
+I. References  
+   1. Internal
+   1. External
+      1. Author, Title, Date, Location
+      1. URI
+I. Images
+
+Blocks of texts are organised in an hierarchy (a1).  
+Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
+A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
+A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
+I leave it to some higher power whether images (e) are required.  
+The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
+
+That's it.  
+
+'But I need to highlight some description text.' No, you don't.  
+If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
+USE CAPS.  
+o r  s p a c e.  
+O R  B O T H.
+
+You haven't seen anything. Continue your walk.
+"""]]

Added a comment: A book writer needs a Fountain pen. Not a printing press.
--- /dev/null	2015-03-31 20:16:00.000000000 +0000
+++ wikisrc/projects/project/troff/comment_2_7d584605c507d311332b26bf85db48d1._comment	2015-03-31 20:19:55.000000000 +0000
@@ -0,0 +1,57 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnS9MXV-DSX3wWkDMT89H2gprV74wkUVeY"
+ nickname="Benjamin"
+ subject="A book writer needs a Fountain pen. Not a printing press."
+ date="2015-03-31T20:18:36Z"
+ content="""
+Thoughts from a passers-by:
+
+Let the output formats (we need most!) dictate the requirements of the tool.  
+Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.  
+Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.  
+If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.  
+Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!  
+
+A writer needs a tool which concentrates his thought. A printing press expands thought.  
+What will the writer do if one gives the writer a printing press?  
+
+Why should the available book formats define the pen of the writer?
+'Content rules format.'  
+
+I see a collection of printing presses. They can do a lot.  
+I read: They don't do the job 'software documentation'.  
+But what does this all have to do with solving the task 'software documentation'?  
+Nothing. One needs to specify what 'software documentation' is before choosing the tool.  
+To me it is:
+
+I. Hierarchy  
+   1. Headings  
+   1. Lists  
+I. Descriptive text
+I. Non-descriptive text (quotes)
+   1. Inline
+   1. Multiline
+I. References  
+   1. Internal
+   1. External
+      1. Author, Title, Date, Location
+      1. URI
+I. Images
+
+Blocks of texts are organised in an hierarchy (a1).  
+Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).  
+A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).  
+A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.  
+I leave it to some higher power whether images (e) are required.  
+The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).
+
+That's it.  
+
+'But I need to highlight some description text.' No, you don't.  
+If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:  
+USE CAPS.  
+o r  s p a c e.  
+O R  B O T H.
+
+You haven't seen anything. Continue your walk.
+"""]]

Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/ports/evbarm/allwinner.mdwn	23 Mar 2015 18:46:00 -0000	1.48
+++ wikisrc/ports/evbarm/allwinner.mdwn	29 Mar 2015 21:33:24 -0000	1.49
@@ -1,5 +1,7 @@
 [[!meta title="NetBSD/evbarm on Allwinner Technology SoCs"]]
 
+NetBSD 7.0 has support for A10, A20, and A31 SoCs. NetBSD -current adds support for A80 SoCs.
+
 [[!toc levels=2]]
 
 # Supported boards

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	18 Mar 2015 18:52:45 -0000	1.38
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	29 Mar 2015 21:32:29 -0000	1.39
@@ -1,11 +1,13 @@
 [[!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.
+
+Initial 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.
+
 [[images/raspberrypi.jpg]]
 
 [[!toc levels=2]]
 
-This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
-
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
 
 # Installation

Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/ports/evbarm/odroid-c1.mdwn	29 Mar 2015 21:23:32 -0000	1.12
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	29 Mar 2015 21:29:58 -0000	1.13
@@ -1,5 +1,7 @@
 [[!meta title="NetBSD/evbarm on Hardkernel ODROID-C1"]]
 
+[ODROID-C1](http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433&tab_idx=1) is a $35 quad-core SBC from Hardkernel. ODROID-C1 support was introduced in NetBSD 7.0.
+
 [[!toc levels=2]]
 
 # Supported hardware

Ethernet and RTC are supported
Index: wikisrc/ports/evbarm/rockchip.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/rockchip.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/evbarm/rockchip.mdwn	5 Jan 2015 11:04:28 -0000	1.1
+++ wikisrc/ports/evbarm/rockchip.mdwn	29 Mar 2015 21:25:53 -0000	1.2
@@ -19,3 +19,5 @@
    - ACT8834
  - Watchdog timer
  - USB host (DWC2)
+ - Ethernet
+ - RTC

link to soc datasheet
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 17:36:52 -0000	1.11
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	29 Mar 2015 21:23:32 -0000	1.12
@@ -141,6 +141,10 @@
 
 To set this value at boot, you can add **fb.scale=95** to the kernel cmdline options in *boot.ini*.
 
+# Documentation
+
+Amlogic S805 datasheet: <http://dn.odroid.com/S805/Datasheet/S805_Datasheet%20V0.8%2020150126.pdf>
+
 # ODROID-C1 UART pins
 
 From [ODROID Forum](http://forum.odroid.com/viewtopic.php?f=115&t=7684):

Note that the supported hardware list is not comprehensive and offer a link to sys/arch/evbarm/conf for a full list of configs.
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/ports/evbarm.mdwn	18 Mar 2015 18:54:55 -0000	1.17
+++ wikisrc/ports/evbarm.mdwn	29 Mar 2015 21:18:29 -0000	1.18
@@ -16,6 +16,8 @@
 """
 supported_hardware="""
 
+**NOTE**: This list is incomplete. For a full list of configurations, please see the [evbarm kernel configs](http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/evbarm/conf/) directory in CVS.
+
 [[!toc startlevel=3]]
 
 ### ADI Engineering **BRH** ("Big Red Head") 

fix typo in previous, and fold another line.
Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:34:56 -0000	1.7
+++ wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:38:30 -0000	1.8
@@ -18,8 +18,7 @@
 low level kernel groveling tools. Additionally, NetBSD/sparc64 is able to run
 Solaris 64 and 32 bit binaries with emulation. See
 [compat_netbsd32(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386),
-[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbs
-d32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbsd32_compat16/README.html).
+[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbsd32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbsd32_compat16/README.html).
 
 Martin Husemann is the maintainer for NetBSD/sparc64.
 """
@@ -80,7 +79,7 @@
 * For older 32 bit SPARC-based machines, see [NetBSD/sparc](../sparc/).
 * [NetBSD/sparc64 FAQ](http://www.NetBSD.org/ports/sparc64/faq.html)
 * [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html)
-* [NetBSD/sparc64 History](http://www.NetBSD.org/ports/sparct64/history.html)
+* [NetBSD/sparc64 History](http://www.NetBSD.org/ports/sparc64/history.html)
 * The [NetBSD Diskless HOWTO](http://www.NetBSD.org/docs/network/netboot/)
 * [Developers and Development Funding](http://www.NetBSD.org/ports/sparc64/development.html)
 * [NetBSD/sparc64 Projects](http://www.NetBSD.org/ports/sparc64/projects.html)

fix a bunch more links that got broken in the conversion to wikisrc,
prompted by a comment i just noticed (thanks, gareth!)
while here, fold some lines (uh...) to fix manpage links and update
text to reflect the fact that petrov is no longer around.
Members: 
	ports/sparc64.mdwn:1.6->1.7 

Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:17:12 -0000	1.6
+++ wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:34:56 -0000	1.7
@@ -7,7 +7,7 @@
 thumbnail="http://www.netbsd.org/images/ports/sparc64/e250u10.gif"
 about="""
 NetBSD/sparc64 is a NetBSD port to Sun's 64-bit UltraSPARC machines. The first
-binary release for sparc64 was [NetBSD 1.5](../../releases/formal-1.5/).
+binary release for sparc64 was [NetBSD 1.5](http://www.NetBSD.org/releases/formal-1.5/).
 NetBSD/sparc64 supports many systems, including Sbus-based UltraSPARC systems
 and PCI-based UltraSPARC systems using UltraSPARC I, II, IIi, and IIe CPU
 types.
@@ -17,14 +17,11 @@
 support for running most 32-bit binaries as well, with the exception of some
 low level kernel groveling tools. Additionally, NetBSD/sparc64 is able to run
 Solaris 64 and 32 bit binaries with emulation. See
-[compat_netbsd32(8)](http://netbsd.gw.com/cgi-bin/man-
-cgi?compat_netbsd32+8+NetBSD-5.1+i386),
-[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-
-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbs
-d32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbs
-d32_compat16/README.html).
+[compat_netbsd32(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386),
+[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbs
+d32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbsd32_compat16/README.html).
 
-Martin Husemann and Andrey Petrov are the maintainers for NetBSD/sparc64.
+Martin Husemann is the maintainer for NetBSD/sparc64.
 """
 supported_hardware="""
 Clones based on any of these systems should also work
@@ -65,9 +62,9 @@
 * All on-board parallel ports 
 * Most input devices (keyboards, mice, trackballs). 
 * Audio 
-* Most Machine-independent [SBUS cards](../../support/hardware/sbus.html)
-* Most Machine-independent [PCI cards](../../support/hardware/pci.html)
-* Most Machine-independent [USB device](../../support/hardware/usb.html)
+* Most Machine-independent [SBUS cards](http://www.NetBSD.org/support/hardware/sbus.html)
+* Most Machine-independent [PCI cards](http://www.NetBSD.org/support/hardware/pci.html)
+* Most Machine-independent [USB device](http://www.NetBSD.org/support/hardware/usb.html)
 * FireWire 
 """
 unsupported_hardware="""
@@ -78,16 +75,16 @@
 """
 additional="""
 For frequently asked questions and links to Sun hardware information, see the
-[NetBSD/sparc64 FAQ](faq.html).
+[NetBSD/sparc64 FAQ](http://www.NetBSD.org/ports/sparc64/faq.html).
 
 * For older 32 bit SPARC-based machines, see [NetBSD/sparc](../sparc/).
-* [NetBSD/sparc64 FAQ](faq.html)
-* [Notes on System Models](models.html)
-* [NetBSD/sparc64 History](history.html)
-* The [NetBSD Diskless HOWTO](../../docs/network/netboot/)
-* [Developers and Development Funding](development.html)
-* [NetBSD/sparc64 Projects](projects.html)
-* [Running NetBSD on emulated hardware](../emulators.html)
+* [NetBSD/sparc64 FAQ](http://www.NetBSD.org/ports/sparc64/faq.html)
+* [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html)
+* [NetBSD/sparc64 History](http://www.NetBSD.org/ports/sparct64/history.html)
+* The [NetBSD Diskless HOWTO](http://www.NetBSD.org/docs/network/netboot/)
+* [Developers and Development Funding](http://www.NetBSD.org/ports/sparc64/development.html)
+* [NetBSD/sparc64 Projects](http://www.NetBSD.org/ports/sparc64/projects.html)
+* [Running NetBSD on emulated hardware](http://www.NetBSD.org/ports/emulators.html)
 """
 ]]
 [[!tag tier1port]]

fix link to "notes on system models" that was broken in the wikification.
XXX this is now a direct link to the htdocs version. ideally that page
should be wikified.
Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/sparc64.mdwn	6 Oct 2014 21:41:29 -0000	1.5
+++ wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:17:12 -0000	1.6
@@ -48,7 +48,7 @@
 * SPARCengine Ultra AXi family (Netra X1, Fire v100, Fire v120, Netra 120, Netra AC 200, Netra DC 200) 
 * SPARCengine Ultra AXe system board 
 
-See the [Notes on System Models](models.html) page for a complete list.
+See the [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html) page for a complete list.
 
 ### All on-board and most optional Sun brand framebuffers 
 

Index: wikisrc/users/billc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/billc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/billc.mdwn	20 Mar 2015 00:45:34 -0000	1.2
+++ wikisrc/users/billc.mdwn	25 Mar 2015 00:52:41 -0000	1.3
@@ -4,3 +4,20 @@
 @Cryo on Twitter
 Cryo on irc.freenode.net
 Cryo+ on plus.google.com
+
+
+==Experience of getting NetBSD-7 running on eeepc900==
+
+VERY IMPORTANT
+*Can not configure network with WIFI with sysinst during install.  Configure network will not use wpa_supplicant or wiconfig and
+does not differentiate between ethernet in WIFI in displaying interfaces.  This gives a false impression that if you configure ath0
+that it will ask for SSID, Encryption Type, and Password and generate /etc/wpa_supplicant.conf as well as add the necessary
+parts to rc.conf.  The fact that wpa_supplicant can't accept this information from the command line and requires a conf file may
+be part of the problem.
+
+IMPORTANT
+*DRMKMS kernel will choose other display, I guess, because the LCD will go black or weird fade to black.
+
+NOT IMPORTANT
+*SDCard class 10, seems rather slow on the USB bus, like slower than on other OS I have run on it... is this not enough wakeups
+on the USB driver?

Use mainline U-Boot for A31
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- wikisrc/ports/evbarm/allwinner.mdwn	3 Feb 2015 10:11:59 -0000	1.47
+++ wikisrc/ports/evbarm/allwinner.mdwn	23 Mar 2015 18:46:00 -0000	1.48
@@ -71,8 +71,7 @@
 
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
 * Download a U-Boot build for your board
-  * A10/A20: Download from the linux-sunxi web site <http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi-mainline/u-boot-sunxi-mainline-latest/>
-  * A31: The standard u-boot-sunxi tree doesn't support A31 yet. Until sun6i support is merged, a build is available at <http://www.invisible.ca/allwinner/a31/> 
+  * Download the correct build from the linux-sunxi web site <http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi-mainline/u-boot-sunxi-mainline-latest/>.
 * Write the *u-boot-sunxi-with-spl.bin* loader to the empty space at the start of the base image:
 [[!template  id=programlisting text="""
 # dd if=u-boot-sunxi-with-spl.bin of=beagleboard.img bs=1k seek=8 conv=notrunc

Add RTC to supported hardware list
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:35:35 -0000	1.10
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 17:36:52 -0000	1.11
@@ -17,6 +17,7 @@
  - Gigabit Ethernet (GMAC)
    - RTL8211F PHY
  - Hardware random number generator
+ - RTC
 
 # TODO
  - USB device mode

Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:31:34 -0000	1.9
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:35:35 -0000	1.10
@@ -110,6 +110,10 @@
 
 # HDMI
 
+## Framebuffer console
+
+Simply add **console=fb** to the *bootargs* variable in *boot.ini*.
+
 ## Video mode
 
 HDMI video mode can be selected in U-Boot with the *video* command, e.g.:

Add video mode section
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 14:01:40 -0000	1.8
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:31:34 -0000	1.9
@@ -67,14 +67,10 @@
 """]]
 * Write the image to an SD card.
 * Copy the kernel (netbsd.ub) for your board to the root of the MS-DOS partition on the SD card.
-* Create or edit boot.ini on the MS-DOS partition:
+* Create or edit *boot.ini* on the MS-DOS partition:
 [[!template  id=programlisting text="""
 ODROIDC-UBOOT-CONFIG
 
-setenv m "1080p"
-setenv vout_mode "hdmi"
-setenv m_bpp "32"
-setenv disableuhs "disableuhs"
 setenv bootargs "root=ld0f awge0.mac-address=${ethaddr}"
 setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 run bootcmd
@@ -112,7 +108,23 @@
 # reboot
 """]]
 
-# Overscan compensation
+# HDMI
+
+## Video mode
+
+HDMI video mode can be selected in U-Boot with the *video* command, e.g.:
+
+[[!template  id=programlisting text="""
+odroidc#video dev open 1080P
+"""]]
+
+To make this change permanent, add it to the *bootcmd* variable in *boot.ini*:
+
+[[!template  id=programlisting text="""
+setenv bootcmd "video dev open 1080P; fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
+"""]]
+
+## Overscan compensation
 
 If you have ODROID-C1 plugged into a TV, the edges of the screen may not be visible. You can scale down the framebuffer console with the **hw.genfb0.scale** sysctl, e.g.:
 

Added a comment: NetBSD error
--- /dev/null	2015-03-22 14:32:00.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_5_e342e8f4927d08f4a1f9e22df21d1930._comment	2015-03-22 14:37:57.000000000 +0000
@@ -0,0 +1,15 @@
+[[!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
+"""]]

Overscan compensation
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/evbarm/odroid-c1.mdwn	21 Mar 2015 10:56:12 -0000	1.7
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 14:01:40 -0000	1.8
@@ -112,6 +112,18 @@
 # reboot
 """]]
 
+# Overscan compensation
+
+If you have ODROID-C1 plugged into a TV, the edges of the screen may not be visible. You can scale down the framebuffer console with the **hw.genfb0.scale** sysctl, e.g.:
+
+[[!template  id=programlisting text="""
+# sysctl -w hw.genfb0.scale=95
+"""]]
+
+Setting *scale* to 100 disables scaling, any other value enables the scaler. Values between 10 and 100 are allowed.
+
+To set this value at boot, you can add **fb.scale=95** to the kernel cmdline options in *boot.ini*.
+
 # ODROID-C1 UART pins
 
 From [ODROID Forum](http://forum.odroid.com/viewtopic.php?f=115&t=7684):

Framebuffer console is supported
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/evbarm/odroid-c1.mdwn	16 Mar 2015 21:42:59 -0000	1.6
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	21 Mar 2015 10:56:12 -0000	1.7
@@ -12,6 +12,7 @@
  - A5 global timer
  - SD/MMC controller (DMA)
  - Serial console
+ - Framebuffer console
  - USB host (OTG)
  - Gigabit Ethernet (GMAC)
    - RTL8211F PHY
@@ -21,10 +22,10 @@
  - USB device mode
  - Simultaneous SD card and eMMC usage
  - SD/MMC UHS-I support (needs sdmmc(4) changes)
- - HDMI / framebuffer
  - IR receiver
  - GPIO
  - I2C
+ - Audio
 
 # Installation
 

Index: wikisrc/users/billc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/billc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/billc.mdwn	4 Jul 2010 13:28:25 -0000	1.1
+++ wikisrc/users/billc.mdwn	20 Mar 2015 00:45:34 -0000	1.2
@@ -1,3 +1,6 @@
 Otherwise known as &quot;Cryo&quot;.
 
 <http://cryo.ws>
+@Cryo on Twitter
+Cryo on irc.freenode.net
+Cryo+ on plus.google.com

Mention rpi2
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/evbarm.mdwn	16 Mar 2015 21:42:15 -0000	1.16
+++ wikisrc/ports/evbarm.mdwn	18 Mar 2015 18:54:55 -0000	1.17
@@ -205,8 +205,8 @@
  * Other devices inserted into the PCI/mPCI slot
  * On-chip watchdog timer (_ixpwdog_)
 
-### Raspberry Pi Foundation **Raspberry Pi**
-The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation.
+### Raspberry Pi Foundation **Raspberry Pi**/**Raspberry Pi 2**
+The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation. Both the Raspberry Pi and Raspberry Pi 2 are supported.
 
 ### Rockchip PX2/RK3066/RK3188/RK3188+
 Various [[Rockchip]] family SoCs are supported by the ROCKCHIP kernel.

RPI2 is part of NetBSD 7 now
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:45:15 -0000	1.37
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	18 Mar 2015 18:52:45 -0000	1.38
@@ -10,8 +10,7 @@
 
 # Installation
  - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended. This isn't optimized for Raspberry Pi 2, but allows a single image to be used for all boards.
-   - The Raspberry Pi port will be part of the NetBSD 7 release.
-   - The Raspberry Pi 2 port is only in HEAD at present.
+   - The Raspberry Pi and Pi 2 ports will be part of the NetBSD 7 release.
    - The automatic nightly builds can be found in the 'evbarm-earmv6hf/binary/gzimg/' directory on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).
      - The stable build will be under netbsd-7/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/
      - The HEAD/current build will be under HEAD/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/

add another page that needs updating
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/releng/release-prep.mdwn	24 Jan 2015 07:49:06 -0000	1.18
+++ wikisrc/releng/release-prep.mdwn	17 Mar 2015 05:10:22 -0000	1.19
@@ -151,6 +151,7 @@
     - Update htdocs/releases/formal-&lt;blah&gt;/index.xml
     - Update htdocs/mirrors/torrents/
     - Update htdocs/releases/formal.xml
+    - Update htdocs/about/history.xml
     - Top-level regen of everything
     - Update htdocs/changes/index.xml
     - Update htdocs/index.html

Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:48:58 -0000	1.5
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	16 Mar 2015 21:42:59 -0000	1.6
@@ -3,7 +3,7 @@
 [[!toc levels=2]]
 
 # Supported hardware
- - CPU: Cortex-A5: S805 (4-core) at 1.5GHz
+ - CPU: Cortex-A5: Amlogic S805 (4-core) at 1.5GHz
    - CPU frequency scaling is supported with machdep.cpu sysctl tree
    - SMP supported
    - PL310 L2 cache controller

xref odroid-c1
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/evbarm.mdwn	5 Jan 2015 11:05:36 -0000	1.15
+++ wikisrc/ports/evbarm.mdwn	16 Mar 2015 21:42:15 -0000	1.16
@@ -110,6 +110,10 @@
  * GPSstix (GPS not test)
  * tweener
 
+### Hardkernel ODROID-C1
+
+The [[ODROID-C1]] is a quad core Cortex-A5 small form-factor board from Hardkernel co., Ltd.
+
 ### Intel **DBPXA250** ("Lubbock") 
 
 DBPXA250 (a.k.a. Lubbock) is an evaluation and development platform for the

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:57:21 -0000	1.18
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	16 Mar 2015 07:20:41 -0000	1.19
@@ -9,7 +9,7 @@
 First Last | `login@` | comment(s)
 Bernd Ernesti | `veego` |
 David Maxwell | `david` |
-Hiroki Suenaga | `hsuenaga` |
+Jun Ebihara | `jun` |
 Justin Cormack | `justin` |
 Kengo Nakahara | `knakahara` |
 Kenichi Hashimoto | `hkenken` | will be late.

alphabetical order by name
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:54:20 -0000	1.17
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:57:21 -0000	1.18
@@ -16,12 +16,12 @@
 Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |
+Masao Uebayashi | `uebayasi` |
 Masaru OKI | `oki` |
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
 Taylor R Campbell | `riastradh` |
-Masao Uebayashi | `uebayasi` |
 """]]
 
 ## Planning to present something?

Added uebayasi.
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 13:10:53 -0000	1.16
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:54:20 -0000	1.17
@@ -21,6 +21,7 @@
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
 Taylor R Campbell | `riastradh` |
+Masao Uebayashi | `uebayasi` |
 """]]
 
 ## Planning to present something?

adjust PAE comments
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -r1.100 -r1.101
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:29:11 -0000	1.100
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 23:40:07 -0000	1.101
@@ -140,10 +140,10 @@
 should in theory work.  An amd64 xen/dom0 is known to support both
 i386 and amd64 domUs.
 
-Except for an odd case with Xen 3.1, i386 dom0 and domU kernels must
-be PAE; these are built by default.  (Note that emacs (at least) fails
-if run on i386 with PAE when built without, and vice versa, presumably
-due to bugs in the undump code.)
+i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
+built by default.  (Note that emacs (at least) fails if run on i386
+with PAE when built without, and vice versa, presumably due to bugs in
+the undump code.)
 
 Because of the above, the standard approach is to use amd64 for the
 dom0.

Tweak previous
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:27:36 -0000	1.99
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:29:11 -0000	1.100
@@ -149,8 +149,9 @@
 dom0.
 
 Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
-if this is about the CPU having to be amd64, or about the dom0 kernel
-having to be amd64.
+if this is about the CPU, the xen kernel, or the dom0 kernel having to
+be amd64.
+
 
 Stability
 ---------

Explain the i386/amd64 situation more clearly and more accurately.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:21:22 -0000	1.98
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:27:36 -0000	1.99
@@ -130,20 +130,28 @@
 ------------
 
 Xen itself can run on i386 or amd64 machines.  (Practically, almost
-any computer where one would want to run Xen supports amd64.)  If
-using an i386 NetBSD kernel for the dom0, PAE is required (PAE
-versions are built by default).  While i386 dom0 works fine, amd64 is
-recommended as more normal.
+any computer where one would want to run Xen today supports amd64.)
+
+Xen, the dom0 kernel, and each domU kernel can be either i386 or
+amd64.  When building a xenkernel package, one obtains i386 on an i386
+host, and amd64 on an amd64 host.  If the xen kernel is i386, then the
+dom0 kernel and all domU kernels must be i386.  With an amd64 xen
+kernel, an amd64 dom0 kernel is known to work, and an i386 dom0 kernel
+should in theory work.  An amd64 xen/dom0 is known to support both
+i386 and amd64 domUs.
+
+Except for an odd case with Xen 3.1, i386 dom0 and domU kernels must
+be PAE; these are built by default.  (Note that emacs (at least) fails
+if run on i386 with PAE when built without, and vice versa, presumably
+due to bugs in the undump code.)
+
+Because of the above, the standard approach is to use amd64 for the
+dom0.
 
 Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
 if this is about the CPU having to be amd64, or about the dom0 kernel
 having to be amd64.
 
-One can then run i386 domUs and amd64 domUs, in any combination.  If
-running an i386 NetBSD kernel as a domU, the PAE version is required.
-(Note that emacs (at least) fails if run on i386 with PAE when built
-without, and vice versa, presumably due to bugs in the undump code.)
-
 Stability
 ---------
 

fix spacing/tabs for literal text
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -r1.97 -r1.98
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:20:17 -0000	1.97
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:21:22 -0000	1.98
@@ -533,7 +533,7 @@
 
 Older hardware:
 
-	Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
+        Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
 
 Running Xen under qemu
 ----------------------

Add some mobo/cpu combos
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -r1.96 -r1.97
--- wikisrc/ports/xen/howto.mdwn	11 Mar 2015 17:17:35 -0000	1.96
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:20:17 -0000	1.97
@@ -516,6 +516,24 @@
 correct set of daemons.  Ensure that the domU config files are valid
 for the new version.
 
+Hardware known to work
+----------------------
+
+Arguably, this section is misplaced, and there should be a page of
+hardware that runs NetBSD/amd64 well, with the mostly-well-founded
+assumption that NetBSD/xen runs fine on any modern hardware that
+NetBSD/amd64 runs well on.  Until then, we give motherboard/CPU/RAM
+triples to aid those choosing a motherboard.  Note that Xen systems
+usually do not run X, so a listing here does not imply that X works at
+all.
+
+        Supermicro X9SRL-F, Xeon E5-1650 v2, 96 GiB ECC
+        Supermicro ??, Atom C2758 (8 core), 32 GiB ECC
+        ASUS M5A78L-M/USB3 AM3+ microATX, AMD Piledriver X8 4000MHz, 16 GiB ECC
+
+Older hardware:
+
+	Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
 
 Running Xen under qemu
 ----------------------

Add XSA page.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -r1.95 -r1.96
--- wikisrc/ports/xen/howto.mdwn	5 Mar 2015 14:04:55 -0000	1.95
+++ wikisrc/ports/xen/howto.mdwn	11 Mar 2015 17:17:35 -0000	1.96
@@ -95,6 +95,8 @@
 xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and
 not yet recommended for other than experimental/testing use.
 
+See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
+
 Ideally newer versions of Xen will be added to pkgsrc.
 
 Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 05:25:19 -0000	1.15
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 13:10:53 -0000	1.16
@@ -30,7 +30,7 @@
 `all` | Self introduction (5minutes in each person)
 `msaitoh@` | New NetBSD developer candidates(10-15 minutes)
 `msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
-`mef@` | (pkgsrc) New trial: Getting list of updated status (15 minutes)
+`mef@` | (pkgsrc) New trial: [Getting list of updated status](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html) (15 minutes)
 `login@` |_Very Interesting Thing_
 """]]
 

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/mef.mdwn	11 Mar 2015 13:03:40 -0000	1.5
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:06:33 -0000	1.6
@@ -1,3 +1,5 @@
 Makoto Fujiwara (pkgsrc)
 # project
 [check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)
+# PR not submitted
+# PR submitted or concerned

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/mef.mdwn	11 Mar 2015 13:02:03 -0000	1.4
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:03:40 -0000	1.5
@@ -1,2 +1,3 @@
 Makoto Fujiwara (pkgsrc)
-* [check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)
+# project
+[check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/mef.mdwn	11 Mar 2015 13:00:53 -0000	1.3
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:02:03 -0000	1.4
@@ -1,2 +1,2 @@
 Makoto Fujiwara (pkgsrc)
-* [http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html](check-update)
+* [check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/mef.mdwn	11 Mar 2015 12:59:44 -0000	1.2
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:00:53 -0000	1.3
@@ -1,2 +1,2 @@
 Makoto Fujiwara (pkgsrc)
-* http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html[check-update]
+* [http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html](check-update)

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/mef.mdwn	11 Mar 2015 12:58:04 -0000	1.1
+++ wikisrc/users/mef.mdwn	11 Mar 2015 12:59:44 -0000	1.2
@@ -1 +1,2 @@
 Makoto Fujiwara (pkgsrc)
+* http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html[check-update]

--- /dev/null	2015-03-11 12:50:01.000000000 +0000
+++ wikisrc/users/mef.mdwn	2015-03-11 12:58:08.000000000 +0000
@@ -0,0 +1 @@
+Makoto Fujiwara (pkgsrc)

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	9 Mar 2015 01:14:57 -0000	1.14
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 05:25:19 -0000	1.15
@@ -9,7 +9,6 @@
 First Last | `login@` | comment(s)
 Bernd Ernesti | `veego` |
 David Maxwell | `david` |
-Hikaru Abe | `hikaru` |
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
 Kengo Nakahara | `knakahara` |

Update qemu bug reference to refer to the sparc specific one.
Index: wikisrc/kernel_debugging_with_qemu.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kernel_debugging_with_qemu.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/kernel_debugging_with_qemu.mdwn	19 Feb 2015 09:37:14 -0000	1.9
+++ wikisrc/kernel_debugging_with_qemu.mdwn	10 Mar 2015 07:36:40 -0000	1.10
@@ -31,8 +31,7 @@
 script.  The i386 port is the preferred test platform because the two
 other ports supported by anita are affected by known bugs: amd64 by
 [[PR 49276|http://gnats.NetBSD.org/49276]], and sparc by
-[[qemu bug 1335444|https://bugs.launchpad.net/qemu/+bug/1335444]].
-
+[[qemu bug 1399943|https://bugs.launchpad.net/qemu/+bug/1399943]].
 If you do the build in a directory other than /usr/src, 
 use the -fdebug-prefix-map option to ensure that the source file names embedded
 in the debug symbols point to /usr/src, which is where the sources will be

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:43:59 -0000	1.36
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:45:15 -0000	1.37
@@ -142,3 +142,4 @@
 
 # What needs work
  - USB (host); isochronous transfers.
+ - MULTIPROCESSOR support for Raspberry Pi 2

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Feb 2015 21:10:46 -0000	1.35
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:43:59 -0000	1.36
@@ -4,13 +4,14 @@
 
 [[!toc levels=2]]
 
-This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).
+This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
 
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
 
 # Installation
- - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended.
+ - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended. This isn't optimized for Raspberry Pi 2, but allows a single image to be used for all boards.
    - The Raspberry Pi port will be part of the NetBSD 7 release.
+   - The Raspberry Pi 2 port is only in HEAD at present.
    - The automatic nightly builds can be found in the 'evbarm-earmv6hf/binary/gzimg/' directory on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).
      - The stable build will be under netbsd-7/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/
      - The HEAD/current build will be under HEAD/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/

Added a comment: Great job!
--- /dev/null	2015-03-09 05:50:01.000000000 +0000
+++ wikisrc/ports/evbarm/odroid-c1/comment_1_05bcc1009bf23342220dacdfe6e8dcc1._comment	2015-03-09 05:54:43.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnLCothbjAqByE8Ibp4T2U73QJAVPRvpQc"
+ nickname="Bo"
+ subject="Great job!"
+ date="2015-03-09T05:53:26Z"
+ content="""
+Really looking forward to the future of this port!  I'd love to build a fileserver with my C1 using NetBSD as the OS.
+"""]]

fix typo
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 22:37:14 -0000	1.13
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	9 Mar 2015 01:14:57 -0000	1.14
@@ -21,7 +21,7 @@
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
-Taylor R Campbell | `raiastradh` |
+Taylor R Campbell | `riastradh` |
 """]]
 
 ## Planning to present something?

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 18:21:19 -0000	1.12
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 22:37:14 -0000	1.13
@@ -8,6 +8,7 @@
 [[!table data="""
 First Last | `login@` | comment(s)
 Bernd Ernesti | `veego` |
+David Maxwell | `david` |
 Hikaru Abe | `hikaru` |
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |

Add NetBSD presentaion in work-in-progress session.
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 06:09:06 -0000	1.11
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 18:21:19 -0000	1.12
@@ -36,3 +36,4 @@
 
 ## Discussions
 * board voting procedure
+* NetBSD presentaion in work-in-progress session.

typo
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:44:02 -0000	1.4
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:48:58 -0000	1.5
@@ -78,7 +78,7 @@
 setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 run bootcmd
 """]]
-* On first boot, it will stopbecause of the wrong device in /etc/fstab. Take this opportunity to grow the root file-system:
+* On first boot, it will stop because of the wrong device in /etc/fstab. Take this opportunity to grow the root file-system:
 [[!template  id=programlisting text="""
 # fdisk -u ld0
 ...

Update ODROID-C1 installation instructions.
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 14:21:33 -0000	1.3
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:44:02 -0000	1.4
@@ -31,12 +31,39 @@
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
 * Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
   * Pre-built binaries here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/odroidc1/u-boot-odroidc-v2011.03-20150308.tar.gz>
+* Note the location and size of the FFS partition in the *beagleboard.img* disklabel:
+[[!template  id=programlisting text="""
+# $TOOLDIR/bin/nbdisklabel -M evbarm -B le beagleboard.img
+...
+8 partitions:
+#        size    offset     fstype [fsize bsize cpg/sgs]
+ a:   1359312    385024     4.2BSD      0     0     0  # (Cyl.    188 -    851*)
+ b:    262144    122880       swap                     # (Cyl.     60 -    187)
+ c:   1744336         0     unused      0     0        # (Cyl.      0 -    851*)
+ d:   1744336         0     unused      0     0        # (Cyl.      0 -    851*)
+ e:    114688      8192      MSDOS                     # (Cyl.      4 -     59)
+"""]]
 * Write the bootloader to the empty space at the start of the base image:
 [[!template  id=programlisting text="""
 # dd if=bl1.bin.hardkernel of=beagleboard.img bs=1 count=442 conv=notrunc
 # dd if=bl1.bin.hardkernel of=beagleboard.img bs=512 skip=1 seek=1 conv=notrunc
 # dd if=u-boot.bin of=beagleboard.img bs=512 seek=64 conv=notrunc
 """]]
+* Since the bootloader has overwritten the disklabel, we need to re-add partition "a" from the disklabel to the MBR partition table:
+[[!template  id=programlisting text="""
+# $TOOLDIR/bin/armv7--netbsdelf-eabihf-fdisk -u beagleboard.img
+...
+Which partition do you want to change?: [none] 1
+The data for partition 1 is:
+<UNUSED>
+sysid: [0..255 default: 169] 
+start: [0..109cyl default: 63, 0cyl, 0MB] 385024
+size: [0..85cyl default: 1359312, 85cyl, 664MB] 1359312
+...
+Which partition do you want to change?: [none] 
+...
+Should we write new partition table? [n] y
+"""]]
 * Write the image to an SD card.
 * Copy the kernel (netbsd.ub) for your board to the root of the MS-DOS partition on the SD card.
 * Create or edit boot.ini on the MS-DOS partition:
@@ -47,11 +74,42 @@
 setenv vout_mode "hdmi"
 setenv m_bpp "32"
 setenv disableuhs "disableuhs"
-setenv bootargs "root=ld0a awge0.mac-address=${ethaddr}"
+setenv bootargs "root=ld0f awge0.mac-address=${ethaddr}"
 setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 run bootcmd
 """]]
-
+* On first boot, it will stopbecause of the wrong device in /etc/fstab. Take this opportunity to grow the root file-system:
+[[!template  id=programlisting text="""
+# fdisk -u ld0
+...
+Which partition do you want to change?: [none] 1
+The data for partition 1 is:
+NetBSD (sysid 169)
+    start 385024, size 1359312 (664 MB, Cyls 23/246/32-108/147/55)
+        PBR is not bootable: All bytes are identical (0x00)
+sysid: [0..255 default: 169]
+start: [0..966cyl default: 385024, 24cyl, 188MB]
+size: [0..942cyl default: 1359312, 85cyl, 664MB] $
+...
+Which partition do you want to change?: [none]
+...
+Should we write new partition table? [n] y
+# resize_ffs -y /dev/rld0f
+# reboot
+"""]]
+* Next boot, create a new /etc/fstab:
+[[!template  id=programlisting text="""
+# mount -u -o rw /dev/ld0f /
+# cat > /etc/fstab << EOF
+/dev/ld0f       /               ffs     rw      1 1
+/dev/ld0e       /boot           msdos   rw      1 1
+kernfs          /kern           kernfs  rw
+ptyfs           /dev/pts        ptyfs   rw
+procfs          /proc           procfs  rw
+tmpfs           /var/shm        tmpfs   rw,-m1777,-sram%25
+EOF
+# reboot
+"""]]
 
 # ODROID-C1 UART pins
 

Link to pre-build U-Boot binaries
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 13:34:37 -0000	1.2
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 14:21:33 -0000	1.3
@@ -30,6 +30,7 @@
 
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
 * Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
+  * Pre-built binaries here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/odroidc1/u-boot-odroidc-v2011.03-20150308.tar.gz>
 * Write the bootloader to the empty space at the start of the base image:
 [[!template  id=programlisting text="""
 # dd if=bl1.bin.hardkernel of=beagleboard.img bs=1 count=442 conv=notrunc

ODROID-C1 installation notes, add supported hardware table and TODO list
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/evbarm/odroid-c1.mdwn	27 Feb 2015 17:58:34 -0000	1.1
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 13:34:37 -0000	1.2
@@ -2,6 +2,56 @@
 
 [[!toc levels=2]]
 
+# Supported hardware
+ - CPU: Cortex-A5: S805 (4-core) at 1.5GHz
+   - CPU frequency scaling is supported with machdep.cpu sysctl tree
+   - SMP supported
+   - PL310 L2 cache controller
+ - GIC
+ - A5 watchdog timer
+ - A5 global timer
+ - SD/MMC controller (DMA)
+ - Serial console
+ - USB host (OTG)
+ - Gigabit Ethernet (GMAC)
+   - RTL8211F PHY
+ - Hardware random number generator
+
+# TODO
+ - USB device mode
+ - Simultaneous SD card and eMMC usage
+ - SD/MMC UHS-I support (needs sdmmc(4) changes)
+ - HDMI / framebuffer
+ - IR receiver
+ - GPIO
+ - I2C
+
+# Installation
+
+* Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
+* Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
+* Write the bootloader to the empty space at the start of the base image:
+[[!template  id=programlisting text="""
+# dd if=bl1.bin.hardkernel of=beagleboard.img bs=1 count=442 conv=notrunc
+# dd if=bl1.bin.hardkernel of=beagleboard.img bs=512 skip=1 seek=1 conv=notrunc
+# dd if=u-boot.bin of=beagleboard.img bs=512 seek=64 conv=notrunc
+"""]]
+* Write the image to an SD card.
+* Copy the kernel (netbsd.ub) for your board to the root of the MS-DOS partition on the SD card.
+* Create or edit boot.ini on the MS-DOS partition:
+[[!template  id=programlisting text="""
+ODROIDC-UBOOT-CONFIG
+
+setenv m "1080p"
+setenv vout_mode "hdmi"
+setenv m_bpp "32"
+setenv disableuhs "disableuhs"
+setenv bootargs "root=ld0a awge0.mac-address=${ethaddr}"
+setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
+run bootcmd
+"""]]
+
+
 # ODROID-C1 UART pins
 
 From [ODROID Forum](http://forum.odroid.com/viewtopic.php?f=115&t=7684):

Add mef's presentation
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:09:23 -0000	1.10
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 06:09:06 -0000	1.11
@@ -30,6 +30,7 @@
 `all` | Self introduction (5minutes in each person)
 `msaitoh@` | New NetBSD developer candidates(10-15 minutes)
 `msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
+`mef@` | (pkgsrc) New trial: Getting list of updated status (15 minutes)
 `login@` |_Very Interesting Thing_
 """]]
 

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:01:55 -0000	1.9
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:09:23 -0000	1.10
@@ -27,6 +27,7 @@
 
 [[!table data="""
 Speaker  |Title
+`all` | Self introduction (5minutes in each person)
 `msaitoh@` | New NetBSD developer candidates(10-15 minutes)
 `msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
 `login@` |_Very Interesting Thing_

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 08:21:35 -0000	1.8
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:01:55 -0000	1.9
@@ -1,7 +1,7 @@
 ## Details
 
 The NetBSD developer summit at AsiaBSDCon 2015 will be held Friday,
-09:30-12:30, March 13th.
+09:30-13:00, March 13th. Room E (see [here. The room is at "K"](http://2015.asiabsdcon.org/access.html.en))
 
 ## Planning to attend?
 
@@ -12,6 +12,7 @@
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
 Kengo Nakahara | `knakahara` |
+Kenichi Hashimoto | `hkenken` | will be late.
 Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |

Added a comment
--- /dev/null	2015-03-05 15:32:00.000000000 +0000
+++ wikisrc/pkgsrc/pkgsrc_64bit_osx/comment_3_40bf7235d6c6a251f28f6d9552ca2771._comment	2015-03-05 15:39:04.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmW1g3pl05-P8w5AZNgCwrog-duzcDWucc"
+ nickname="Doug"
+ subject="comment 3"
+ date="2015-03-05T15:37:44Z"
+ content="""
+Thanks, Andrew. That worked.
+"""]]

Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/projects/gsoc.mdwn	17 Feb 2015 01:14:35 -0000	1.17
+++ wikisrc/projects/gsoc.mdwn	5 Mar 2015 14:43:23 -0000	1.18
@@ -10,8 +10,7 @@
 [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010),
 [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of),
 [2012](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of1),
-[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)) and
-we are hoping to once again participate as a mentoring organization in 2015.
+[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)).
 
 This page contains a list of concrete suggestions for projects we would
 like to see applications for in the next Summer of Code. Note that they

Miscellaneous minor edits.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:38:10 -0000	1.94
+++ wikisrc/ports/xen/howto.mdwn	5 Mar 2015 14:04:55 -0000	1.95
@@ -761,7 +761,7 @@
 
         i386 XEN3_DOMU
         i386 XEN3PAE_DOMU
-	amd64 XEN3_DOMU
+        amd64 XEN3_DOMU
 
 Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must
 use the PAE version of the i386 kernel.
@@ -822,8 +822,6 @@
 obtained from the dom0, it is far more likely to be out of sync or
 missing with Xen.)
 
-Your domain should be now ready to work, enjoy.
-
 Creating an unprivileged Linux domain (domU)
 --------------------------------------------
 
@@ -1010,7 +1008,7 @@
 Amazon
 ------
 
-TODO: add link to NetBSD amazon howto.
+See the [Amazon EC2 page](../amazon_ec2/).
 
 Using npf
 ---------
@@ -1018,9 +1016,10 @@
 In standard kernels, npf is a module, and thus cannot be loaded in a
 DOMU kernel.
 
-TODO: explain how to compile npf into a custom kernel, answering (but
-note that the problem was caused by not booting the right kernel):
-http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html
+TODO: Explain how to compile npf into a custom kernel, answering (but
+note that the problem was caused by not booting the right kernel)
+[this email to
+netbsd-users](http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html).
 
 TODO items for improving NetBSD/xen
 ===================================
@@ -1049,6 +1048,5 @@
 TODO: This section contains links from elsewhere not yet integrated
 into the HOWTO.
 
-* [Amazon EC2 (which uses Xen)](../amazon_ec2/).
 * http://www.lumbercartel.ca/library/xen/
 * http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

capitalize HOWTO
Index: wikisrc/ports/xen.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/xen.mdwn	24 Dec 2014 05:35:43 -0000	1.13
+++ wikisrc/ports/xen.mdwn	5 Mar 2015 13:38:58 -0000	1.14
@@ -15,7 +15,8 @@
 guest operating systems with unprecedented levels of performance and resource
 isolation. Xen is Open Source software.
 
-For instructions on how to install Xen with NetBSD, see the [[Xen Howto|/ports/xen/howto]].
+For instructions on how to install Xen with NetBSD, see the
+[[Xen HOWTO|/ports/xen/howto]].
 
 See [http://www.xenproject.org/](http://www.xenproject.org/) for
 more details on Xen.

add another pointer
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:27:37 -0000	1.93
+++ wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:38:10 -0000	1.94
@@ -1049,5 +1049,6 @@
 TODO: This section contains links from elsewhere not yet integrated
 into the HOWTO.
 
+* [Amazon EC2 (which uses Xen)](../amazon_ec2/).
 * http://www.lumbercartel.ca/library/xen/
 * http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

Summary: punctuation
Index: wikisrc/xen.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/xen.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/xen.mdwn	5 Mar 2015 13:28:49 -0000	1.2
+++ wikisrc/xen.mdwn	5 Mar 2015 13:36:42 -0000	1.3
@@ -1,4 +1,4 @@
 # NetBSD on Xen Hypervisor
 
 For information about NetBSD and Xen, see the
-[Xen port page](http://www.netbsd.org/ports/xen/)
+[Xen port page](http://www.netbsd.org/ports/xen/).

Move links to howto. Turn into 302 to port page, basically.
Index: wikisrc/xen.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/xen.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/xen.mdwn	7 Jul 2010 19:14:16 -0000	1.1
+++ wikisrc/xen.mdwn	5 Mar 2015 13:28:49 -0000	1.2
@@ -1,10 +1,4 @@
 # NetBSD on Xen Hypervisor
 
-## Port page for Xen
-<http://www.netbsd.org/ports/xen/>
-
-## Other resources
-
-* <http://www.netbsd.org/ports/xen/howto.html>
-* <http://www.lumbercartel.ca/library/xen/>
-* <http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html>
+For information about NetBSD and Xen, see the
+[Xen port page](http://www.netbsd.org/ports/xen/)

Add a few links, and fix typos.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -r1.92 -r1.93
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:36:07 -0000	1.92
+++ wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:27:37 -0000	1.93
@@ -226,7 +226,7 @@
 desktop or laptop.  Then, one can run domUs at will.  Purists will
 deride this as less secure than the previous approach, and for a
 computer whose purpose is to run domUs, they are right.  But Xen and a
-dom0 (without domUs) is not meaingfully less secure than the same
+dom0 (without domUs) is not meaningfully less secure than the same
 things running without Xen.  One can boot Xen or boot regular NetBSD
 alternately with little problems, simply refraining from starting the
 Xen daemons when not running Xen.
@@ -251,7 +251,7 @@
 partition; this is no different when booting Xen.
 
 There are 4 styles of providing backing storage for the virtual disks
-used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,
+used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN.
 
 With raw partitions, one has a disklabel (or gpt) partition sized for
 each virtual disk to be used by the domU.  (If you are able to predict
@@ -324,6 +324,11 @@
 to force only one vcpu to be provided (since NetBSD dom0 can't use
 more) and to pin that vcpu to a physical cpu.  TODO: benchmark this.
 
+Xen has [many boot
+options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
+and other tham dom0 memory and max_vcpus, they are generally not
+necessary.
+
 As with non-Xen systems, you should have a line to boot /netbsd (a
 kernel that works without Xen) and fallback versions of the non-Xen
 kernel, Xen, and the dom0 kernel.
@@ -1020,8 +1025,10 @@
 TODO items for improving NetBSD/xen
 ===================================
 
-* Package Xen 4.4.
-* Get PCI passthrough working on Xen 4.2 (or 4.4).
+* Make the NetBSD dom0 kernel work with SMP.
+* Test the Xen 4.5 packages adequately to be able to recommend them as
+  the standard approach.
+* Get PCI passthrough working on Xen 4.5
 * Get pvgrub into pkgsrc, either via xentools or separately.
 * grub
   * Check/add support to pkgsrc grub2 for UFS2 and arbitrary
@@ -1033,3 +1040,14 @@
   * Get UFS2 patches into pvgrub.
 * Add support for PV ops to a version of /boot, and make it usable as
   a kernel in Xen, similar to pvgrub.
+* Solve somehow the issue with modules for GENERIC not being loadable
+  in a Xen dom0 or domU kernel.
+
+Random pointers
+===============
+
+TODO: This section contains links from elsewhere not yet integrated
+into the HOWTO.
+
+* http://www.lumbercartel.ca/library/xen/
+* http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:49:37 -0000	1.7
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 08:21:35 -0000	1.8
@@ -7,6 +7,7 @@
 
 [[!table data="""
 First Last | `login@` | comment(s)
+Bernd Ernesti | `veego` |
 Hikaru Abe | `hikaru` |
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
@@ -31,4 +32,4 @@
 """]]
 
 ## Discussions
-*
+* board voting procedure

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:13:46 -0000	1.6
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:49:37 -0000	1.7
@@ -14,6 +14,7 @@
 Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |
+Masaru OKI | `oki` |
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |

Note that /netbsd should exist in a domU for kmem.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -r1.91 -r1.92
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:32:16 -0000	1.91
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:36:07 -0000	1.92
@@ -809,6 +809,14 @@
 in rc.conf. This way, the domain will be properly shut down if
 `xm shutdown -R` or `xm shutdown -H` is used on the dom0.
 
+It is not strictly necessary to have a kernel (as /netbsd) in the domU
+filesystem.  However, various programs (e.g. netstat) will use that
+kernel to look up symbols to read from kernel virtual memory.  If
+/netbsd is not the running kernel, those lookups will fail.  (This is
+not really a Xen-specific issue, but because the domU kernel is
+obtained from the dom0, it is far more likely to be out of sync or
+missing with Xen.)
+
 Your domain should be now ready to work, enjoy.
 
 Creating an unprivileged Linux domain (domU)

Turn PR links into real links.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -r1.90 -r1.91
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:31:02 -0000	1.90
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:32:16 -0000	1.91
@@ -148,8 +148,8 @@
 Mostly, NetBSD as a dom0 or domU is quite stable.
 However, there are some open PRs indicating problems.
 
- - http://gnats.netbsd.org/48125
- - http://gnats.netbsd.org/47720
+ - [PR 48125](http://gnats.netbsd.org/48125)
+ - [PR 47720](http://gnats.netbsd.org/47720)
 
 Note also that there are issues with sparse vnd(4) instances, but
 these are not about Xen.
@@ -526,7 +526,8 @@
         dom0 kernel: NetBSD/amd64 6.1.5
         Xen tools: xentools42-4.2.5 from pkgsrc
 
-See http://gnats.netbsd.org/47720 for a problem with dom0 shutdown.
+See [PR 47720](http://gnats.netbsd.org/47720) for a problem with dom0
+shutdown.
 
 Unprivileged domains (domU)
 ===========================

fix spaces (cosmetic)
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:27:58 -0000	1.89
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:31:02 -0000	1.90
@@ -588,7 +588,7 @@
         xm console foo
         xm create -c foo
         xm shutdown foo
-	xm list
+        xm list
 
 Typing ^] will exit the console session.  Shutting down a domain is
 equivalent to pushing the power button; a NetBSD domU will receive a

Add stability notes.
Reference PRs from gson@ and caution against sparse vnd(4).
Members: 
	ports/xen/howto.mdwn:1.88->1.89 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -r1.88 -r1.89
--- wikisrc/ports/xen/howto.mdwn	10 Feb 2015 17:38:14 -0000	1.88
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:27:58 -0000	1.89
@@ -142,6 +142,18 @@
 (Note that emacs (at least) fails if run on i386 with PAE when built
 without, and vice versa, presumably due to bugs in the undump code.)
 
+Stability
+---------
+
+Mostly, NetBSD as a dom0 or domU is quite stable.
+However, there are some open PRs indicating problems.
+
+ - http://gnats.netbsd.org/48125
+ - http://gnats.netbsd.org/47720
+
+Note also that there are issues with sparse vnd(4) instances, but
+these are not about Xen.
+
 Recommendation
 --------------
 
@@ -636,6 +648,10 @@
 
         dd if=/dev/zero of=foo-xbd0 bs=1m count=4096
 
+Do not use qemu-img-xen, because this will create sparse file.  There
+have been recent (2015) reports of sparse vnd(4) devices causing
+lockups, but there is apparently no PR.
+
 With the lvm style, one creates logical devices.  They are then used
 similarly to vnds.  TODO: Add an example with lvm.
 

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 00:54:01 -0000	1.5
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:13:46 -0000	1.6
@@ -17,6 +17,7 @@
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
+Taylor R Campbell | `raiastradh` |
 """]]
 
 ## Planning to present something?

Add a comment