From bc366dde81f7fb93a540d1e9c8c65e0a414af695 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vin=C3=ADcius=20Ferr=C3=A3o?=
 <2031761+viniciusferrao@users.noreply.github.com>
Date: Fri, 4 Sep 2026 15:31:34 -0300
Subject: [PATCH] docs(genesis): narrow s390x support

---
 .../guides/code/dhcp_backend_validation_matrix.rst         | 7 -------
 .../developers/guides/code/genesis_openembedded_plan.rst   | 7 +++----
 2 files changed, 3 insertions(+), 11 deletions(-)

diff --git a/docs/source/developers/guides/code/dhcp_backend_validation_matrix.rst b/docs/source/developers/guides/code/dhcp_backend_validation_matrix.rst
index 5e80d2876..606d4175a 100644
--- a/docs/source/developers/guides/code/dhcp_backend_validation_matrix.rst
+++ b/docs/source/developers/guides/code/dhcp_backend_validation_matrix.rst
@@ -136,13 +136,6 @@ The following matrix is the default live validation gate for DHCP backend work.
      - ``makedhcp -n``; backend parser; architecture ``0x001f``; DHCP options
        209 and 210; TFTP fetch of the generated ``pxelinux.cfg``-style configuration,
        Genesis kernel, and initramfs
-   * - IBM Z DPM
-     - ``s390x``
-     - ``ISC`` and ``Kea``
-     - configuration handoff only
-     - backend parser; architecture ``0x0020``; generated network configuration
-       offered as the DHCP boot filename; physical boot remains unvalidated
-
 Kea Boot and Reservation Regression Matrix
 ------------------------------------------
 
diff --git a/docs/source/developers/guides/code/genesis_openembedded_plan.rst b/docs/source/developers/guides/code/genesis_openembedded_plan.rst
index 60c518a46..40df7b2b3 100644
--- a/docs/source/developers/guides/code/genesis_openembedded_plan.rst
+++ b/docs/source/developers/guides/code/genesis_openembedded_plan.rst
@@ -99,8 +99,7 @@ and z/VM Genesis networking therefore remain unvalidated.
 Genesis does not use the shared CEC serial as an s390x node identifier.
 QEMU validation covers network IPL, DHCP options 209 and 210, TFTP, and the
 network-specific ``pxelinux.cfg``-style configuration written by ``mknb``.
-For DPM clients, DHCP architecture 32 receives a DPM-formatted configuration
-as its boot filename.  This path has parser coverage but no physical validation.
+This release does not advertise a DPM boot configuration.
 Existing xCAT s390x operating-system provisioning remains unchanged.
 
 xCAT protocol
@@ -285,8 +284,8 @@ References
   <https://kas.readthedocs.io/en/latest/userguide/project-configuration.html>`_
 * `NetworkManager dispatcher interface
   <https://networkmanager.dev/docs/api/latest/NetworkManager-dispatcher.html>`_
-* `IBM Z DPM network boot server configuration
-  <https://www.ibm.com/docs/en/systems-hardware/zsystems/2964-N63?topic=administrators-customizing-network-boot-server-environment>`_
+* `QEMU s390x network boot
+  <https://www.qemu.org/docs/master/system/s390x/bootdevices.html>`_
 * `NetworkManager initrd generator
   <https://networkmanager.dev/docs/api/latest/nm-initrd-generator.html>`_
 * `systemd system extensions