Raspberry Pi network boot DHCP retry timeout configuration

The Raspberry Pi 4 and 5 support PXE network boot via EEPROM settings, yet the bootloader’s DHCP client uses hardcoded retry intervals that cannot be tuned through documented configuration files.

When a DHCP server is slow or a network has high latency, the default five‑retry, two‑second‑interval scheme can cause boot failures or excessive delays. No config.txt option, EEPROM field, or command‑line flag currently exposes these timeouts, and the only documented workaround is to rebuild the bootloader from source.

Given this limitation, what options exist for adjusting the DHCP retry behavior without custom bootloader builds? Is there an upcoming EEPROM parameter that might allow timeout tuning? How can users reliably test and validate any proposed changes on production hardware?