--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2020/10/16 17:35:05	1.138
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	2020/10/16 17:41:50	1.139
@@ -185,7 +185,30 @@ file for the system is loaded by the boo
 
 The RPI bootloader looks for a magic string in a trailer after the kernel to determine if it should use DTB support (the new normal) or something called ATAG (apparently the old way).  See https://github.com/raspberrypi/linux/commit/2367d8a42e2717d8d15a39a9085cc2909fae033a#diff-8f088aca645d10d79b594d58db4136f3e09caee077fe373bb08f02f2040900a9 for more information.
 
+### Kernel format variants
+
+In netbsd-8, only the ELF and bin variants of RPI2 are built.  The bin version is used.
+
+In netbsd-9 releasedir/binary/kernels, the following 4 versions of GENERIC are produced.  (This might be the same in current.)
+
+#### netbsd-GENERIC.gz
+
+This is regular ELF and not used on RPI.
+
+#### netbsd-GENERIC.bin.gz
+
+It is unclear why this file exists on 9.  It seems to be like img, but without the trailer for DTB; this makes sense for 8.
+
+#### netbsd-GENERIC.img.gz
+
+On NetBSD >=9, the kernel with the .img suffix has the trailer to cause the bootloader to load DTB files.
+
+#### netbsd-GENERIC.ub.gz
+
+This is for u-boot and not used on RPI.
+
 ## Configuring 802.11
+
 After installation, the Ethernet will function as on any other NetBSD system; simply enable dhcpcd or configure a static address.  USB WiFi devices will also function as on any other NetBSD system; in addition to dhcpcd or static, configure and enable wpa_supplicant.
 
 Note that the built-in WiFi in the RPI3 is not yet supported.   USB WiFi interfaces (that work on NetBSD in general) should all work.  In particular, the following are known to work: