diff --git a/en/nor-split-layout.md b/en/nor-split-layout.md
index 54210b45..1d993004 100644
--- a/en/nor-split-layout.md
+++ b/en/nor-split-layout.md
@@ -17,6 +17,9 @@ and only their sum has to fit the chip. These SoCs use it:
 |-----|-----------|---------------|------------|----------|
 | GK7205V200, GK7205V300, GK7202V300, GK7605V100 | 256K boot + 64K env | `0x50000` | `u-boot-<soc>-nor.bin` | `-split` and the fixed-slot one |
 | Hi3516CV300, Hi3516EV100 | 256K boot + 64K env | `0x50000` | `u-boot-<soc>-nor.bin` | `-split` and the fixed-slot one |
+| Hi3516EV200, Hi3518EV300, Hi3516DV200 | 256K boot + 64K env | `0x50000` | `u-boot-<soc>-nor.bin` | `-split` and the fixed-slot one |
+| Hi3516EV300 | 256K boot + 64K env | `0x50000` | `u-boot-<soc>-nor.bin` | `-split` only (neo: fixed slots) |
+| GK7205V500, GK7205V510, GK7205V530 | 256K boot + 64K env | `0x50000` | `u-boot-<soc>-nor.bin` | `-split` and the fixed-slot one, both `gk7205v500` |
 | Hi3516CV610, Hi3516CV608 | 256K boot + 64K env | `0x50000` | `boot-<soc>[-<board>]-nor.bin` | `-split` only |
 | Hi3519DV500 | 512K boot + 256K env | `0xC0000` | `boot-hi3519dv500-<board>-nor.bin` | `-split` only |
 
@@ -295,6 +298,9 @@ On the GK7205V200 family: write `uImage.<soc>` at `0x50000` and
 `rootfs.squashfs.<soc>` at the fixed rootfs slot, as in
 [Upgrade firmware](sysupgrade.md) (*From U-Boot*). On a U-Boot environment from
 this bootloader, `run ur; run uk` does the same. The bootloader sees the uImage
-at `0x50000` and boots the fixed slots again. Hi3516CV300 and Hi3516EV100 go
-back the same way. Hi3516CV6xx and Hi3519DV500 are built only for the split
-layout.
+at `0x50000` and boots the fixed slots again. Hi3516CV300, Hi3516EV100,
+Hi3516EV200, Hi3518EV300, Hi3516DV200 and the GK7205V500 family go back the
+same way. Hi3516CV6xx,
+Hi3519DV500 and Hi3516EV300 (lite and ultimate) are built only for the split
+layout: Hi3516EV300's kernel fills the 2 MiB kernel slot, so no fixed-slot
+package of it can ship beside the split one.
diff --git a/en/sysupgrade.md b/en/sysupgrade.md
index 1a6f574e..2e92c489 100644
--- a/en/sysupgrade.md
+++ b/en/sysupgrade.md
@@ -20,15 +20,19 @@ There are other options available so you can use a local copy of the Linux kerne
 
 __ATTENTION! Upgrading firmware can lead to "bricking" your camera. Make sure you are prepared both morally and skill wise. Have your rescue SD card and/or UART adapter ready. Be prepared to de-solder and reprogram flash chip as the last resort. Do not upgrade production cameras unless you really have to!__
 
-On GK7205V200, GK7205V300, GK7202V300 and GK7605V100 with the OpenIPC
-`u-boot-<soc>-nor.bin` bootloader, on Hi3516CV300 and Hi3516EV100 (with that
-bootloader or the older OpenIPC U-Boot 2010.06, which boots the split image as
-well), and on Hi3516CV610, Hi3516CV608 and Hi3519DV500, `sysupgrade -k -r`
-installs the
+On NOR flash: on GK7205V200, GK7205V300, GK7202V300 and GK7605V100 with the
+OpenIPC `u-boot-<soc>-nor.bin` bootloader, on Hi3516CV300 and Hi3516EV100 (with
+that bootloader or the older OpenIPC U-Boot 2010.06, which boots the split image
+as well), on Hi3516EV200, Hi3518EV300 and Hi3516DV200, on Hi3516EV300 lite and
+ultimate (neo keeps fixed slots), on
+GK7205V500, GK7205V510 and GK7205V530, and on Hi3516CV610, Hi3516CV608 and
+Hi3519DV500, `sysupgrade -k -r` installs the
 [NOR split layout](nor-split-layout.md) from `openipc.<soc>-nor-<variant>-split.tgz`
 and carries your settings across (Hi3516CV610 and Hi3516CV608 share one package,
-`openipc.hi3516cv6xx-nor-<variant>-split.tgz`). The offsets in *From U-Boot* below
-are for the fixed-slot layout.
+`openipc.hi3516cv6xx-nor-<variant>-split.tgz`; the GK7205V500 family shares
+`openipc.gk7205v500-nor-<variant>-split.tgz`). The offsets in *From U-Boot* below
+are for the fixed-slot layout. NAND cameras upgrade from the NAND package
+instead, as in [NAND flash layouts](nand-rootfs-layouts.md).
 
 ### Using sysupgrade
 `sysupgrade -k -r` gives you the latest release for your camera, as described above; if you wish to revert to a previous image, or load your own updates, then use any of the options described below.