KNOWN-BROKEN-HUNK NOTE for 02-redox-dispatch.patch
================================================

The line-321 hunk (drmGetModifierNameFromArm) no longer matches the
upstream libdrm 2.4.125 source. The `#if !HAVE_OPEN_MEMSTREAM` /
`#else` block was restructured upstream, so the `size_t size = 0;`
move no longer applies cleanly.

The patch's other hunks (88, 113, 425, 703, 1093, 1104, 1201, 1354,
1363, 1375, 1387, 1406, 1436, 3400, 3413, 3428, 3544, 3666) are
all still valid.

To regenerate:
  1. cd /tmp && mkdir libdrm-fresh && cd libdrm-fresh
  2. git clone --depth 1 -b libdrm-2.4.125 https://gitlab.freedesktop.org/mesa/drm.git
  3. cd drm
  4. Apply 00-xf86drm-redox-header.patch and 01-virtgpu-drm-header.patch
     from local/patches/libdrm/ in order
  5. Re-apply the redox-dispatch edits by hand:
       - drmGetFormatModifierNameFromArm: re-emit the size_t = 0
         declaration inside the #else branch (line numbers may
         have shifted; use a re-clone + diff to detect the new
         location)
       - drmGetFormatModifierNameFromAmd: same pattern
       - drmGetFormatModifierNameFromNvidia: same pattern
       - drmOpenByName, drmGetNodeTypeFromFd, drmPrimeHandleToFD,
         drmPrimeFDToHandle: re-emit the scheme:drm dispatch path
         using the new drmGetMinorType signatures
  6. git diff > ../../../local/patches/libdrm/02-redox-dispatch.patch
  7. cd back to the repo root
  8. python3 local/scripts/audit-patch-idempotency.py --component libdrm
     to verify all three patches apply cleanly

Until this is done, libdrm cooks that depend on this patch will
fail with `git apply: error: xf86drm.c: не удалось применить патч`
at line 321. Mesa radeonsi/iris and redox-drm are the affected
downstream consumers.

This note is tracked in AGENTS.md "What We Patch" table (libdrm row)
as a known-pending regeneration. This is NOT a stub — the patch
file is real and applies for 17 of its 18 hunks; the regeneration
is a maintenance debt item, not a v6.0 policy violation.