[PATCH next 00/45] doc: fix some issues reported by linkcheck

[PATCH next 00/45] doc: fix some issues reported by linkcheck

[Quentin Schulz]

Saw a dead link and made the mistake of running `make linkcheckdocs`.
Now I'm knee-deep in it and cannot ignore all the dead and redirected
links. A day later, I've had enough so this is what I managed to fix in
that time. There are many URLs still redirecting (could be fine, but
needs to be individually checked as some big companies have a tendencies
to redirect to generic pages instead of issuing 404s...) or returning
4xx. The issue is that those 4xx also need to be individually checked
because since the AIpocalypse has started many websites now have web
crawler protection in place and linkcheck will trigger those and be
denied access (or be heavily rate limited).

Please be mindful and only run this script once, save its output and
work on fixing individual errors without rerunning the script, otherwise
we would only participate in hammering websites even more (linkcheck
runs multiple workers in parallel and retries when rate-limited).

Note that linkcheck doesn't check for links in code-blocks so our
instructions may point at dead links also.

At an attempt to avoid tens of people running linkcheck at the same
time, here's the output sorted and filtered on !ok status:

(      android/ab: line   77) redirect  https://source.android.com/devices/tech/ota/ab - permanently to https://source.android.com/docs/core/ota/ab
(    android/avb2: line  181) redirect  https://www.op-tee.org/ - permanently to https://www.trustedfirmware.org/projects/op-tee/
(     android/bcb: line  102) redirect  https://source.android.com/devices/bootloader/boot-reason - permanently to https://source.android.com/docs/core/architecture/bootloader/boot-reason
(     android/bcb: line   99) redirect  https://source.android.com/devices/bootloader - permanently to https://source.android.com/docs/core/architecture/bootloader
(android/boot-image: line  158) redirect  https://source.android.com/devices/bootloader/boot-image-header - permanently to https://source.android.com/docs/core/architecture/bootloader/boot-image-header
(android/boot-image: line  159) broken    https://source.android.com/devices/bootloader/recovery-image - 404 Client Error: Not Found for url: https://source.android.com/devices/bootloader/recovery-image
(android/boot-image: line  160) redirect  https://source.android.com/devices/architecture/dto/partitions - permanently to https://source.android.com/docs/core/architecture/dto/partitions
(android/boot-image: line  165) broken    https://connect.linaro.org/resources/san19/san19-217/ - HTTPSConnectionPool(host='connect.linaro.org', port=443): Max retries exceeded with url: /resources/san19/san19-217/ (Caused by NameResolutionError("HTTPSConnection(host='connect.linaro.org', port=443): Failed to resolve 'connect.linaro.org' ([Errno -2] Name or service not known)"))
(android/fastboot: line  290) redirect  https://developer.android.com/studio/releases/platform-tools - permanently to https://developer.android.com/tools/releases/platform-tools
(        arch/arc: line   32) redirect  https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases - permanently to https://github.com/foss-for-mips-arc-processors/toolchain/releases
(      arch/nios2: line   12) redirect  https://rocketboards.org/foswiki/view/Documentation/NiosIILinuxUserManual - permanently to https://www.rocketboards.org/foswiki/view/Documentation/NiosIILinuxUserManual
(      arch/nios2: line   33) broken    http://www.alterawiki.com/wiki/Sopc2dts - 403 Client Error: Forbidden for url: http://www.alterawiki.com/wiki/Sopc2dts
(      arch/nios2: line    9) broken    https://www.altera.com/products/processors/overview.html - 403 Client Error: Forbidden for url: https://www.altera.com/products/processors/overview.html
(         arch/sh: line   75) broken    http://www.superh-linux.org/ - HTTPConnectionPool(host='www.superh-linux.org', port=80): Max retries exceeded with url: / (Caused by NameResolutionError("HTTPConnection(host='www.superh-linux.org', port=80): Failed to resolve 'www.superh-linux.org' ([Errno -2] Name or service not known)"))
(    arch/x86/x86: line  344) broken    https://uefi.org/acpi/specs - 403 Client Error: Forbidden for url: https://uefi.org/acpi/specs
(    arch/x86/x86: line  348) broken    https://www.acpica.org/downloads - 403 Client Error: Forbidden for url: https://corpredirect.intel.com/Redirector/404Redirector.aspx?404;https://acpica.org/downloads
(board/actions/cubieboard7: line  114) broken    https://pan.baidu.com/s/1uawPr0Jao2HgWFLZCLzHAg#list/path=%2FCubieBoard_Download%2FBoard%2FCubieBoard7%2F%E6%96%B9%E7%B3%96%E6%96%B9%E6%A1%88%E5%BC%80%E5%8F%91%E8%B5%84%E6%96%99%2FImage%2FDebian%2FV2.1-test&parentPath=%2F - Anchor 'list/path%3D/CubieBoard_Download/Board/CubieBoard7/%E6%96%B9%E7%B3%96%E6%96%B9%E6%A1%88%E5%BC%80%E5%8F%91%E8%B5%84%E6%96%99/Image/Debian/V2.1-test%26parentPath%3D/' not found
(board/allwinner/sunxi: line  278) redirect  https://github.com/linux-sunxi/sunxi-tools/raw/master/bin/fel-sdboot.sunxi - with Found to https://raw.githubusercontent.com/linux-sunxi/sunxi-tools/master/bin/fel-sdboot.sunxi
(board/allwinner/sunxi: line   74) broken    https://github.com/crust-firmware/crust/blob/master/README.md#building-the-firmware - Anchor 'building-the-firmware' not found
(board/allwinner/sunxi: line   87) redirect  https://linux-sunxi.org - permanently to https://linux-sunxi.org/Main_Page
(board/amlogic/bananapi-cm4io: line   32) broken    https://wiki.banana-pi.org/Banana_Pi_BPI-CM4 - 522 Server Error: <none> for url: https://wiki.banana-pi.org/Banana_Pi_BPI-CM4
(board/amlogic/bananapi-m2pro: line   22) broken    https://wiki.banana-pi.org/Banana_Pi_BPI-M2_Pro - 522 Server Error: <none> for url: https://wiki.banana-pi.org/Banana_Pi_BPI-M2_Pro
(board/amlogic/bananapi-m2s: line   32) broken    https://wiki.banana-pi.org/Banana_Pi_BPI-M2S - 522 Server Error: <none> for url: https://wiki.banana-pi.org/Banana_Pi_BPI-M2S
(board/amlogic/bananapi-m5: line   21) broken    https://wiki.banana-pi.org/Banana_Pi_BPI-M5 - 522 Server Error: <none> for url: https://wiki.banana-pi.org/Banana_Pi_BPI-M5
(board/amlogic/odroid-c2: line   19) broken    https://wiki.odroid.com - 403 Client Error: Forbidden for url: https://wiki.odroid.com/
(  board/apple/m1: line   50) redirect  https://github.com/AsahiLinux/docs/wiki/SW%3Am1n1 - with Found to https://github.com/AsahiLinux/docs
(  board/apple/m1: line   64) redirect  https://github.com/AsahiLinux/docs/wiki/Developer-Quickstart - with Found to https://github.com/AsahiLinux/docs
(board/armltd/juno: line   17) broken    https://developer.arm.com/documentation/100113/latest - 403 Client Error: Forbidden for url: https://developer.arm.com/documentation/100113/latest
(board/armltd/juno: line   59) redirect  https://github.com/TrustedFirmware-A/trusted-firmware-a/tree/master/tools/fiptool - with Found to https://github.com/TrustedFirmware-A/trusted-firmware-a/tree/main/tools/fiptool
(board/armltd/juno: line   74) redirect  https://github.com/ARM-software/SCP-firmware.git - permanently to https://github.com/ARM-software/SCP-firmware
(board/armltd/juno: line    7) broken    https://developer.arm.com/tools-and-software/development-boards/juno-development-board - 403 Client Error: Forbidden for url: https://developer.arm.com/tools-and-software/development-boards/juno-development-board
(board/armltd/vexpress64: line  114) broken    https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms/Arm%20Architecture%20FVPs - 403 Client Error: Forbidden for url: https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms/Arm%20Architecture%20FVPs
(board/armltd/vexpress64: line  115) broken    https://developer.arm.com/tools-and-software/embedded/arm-development-studio - 403 Client Error: Forbidden for url: https://developer.arm.com/tools-and-software/embedded/arm-development-studio
(board/armltd/vexpress64: line  117) redirect  https://trustedfirmware-a.readthedocs.io/ - with Found to https://trustedfirmware-a.readthedocs.io/en/latest/
(board/beagle/am62_pocketbeagle2: line  120) -ignored- https://git.ti.com/cgit/arago-project/tisdk-setup-scripts/tree/create-sdcard.sh: service unavailable
(board/beagle/am62_pocketbeagle2: line   13) redirect  https://github.com/OP-TEE/optee_os.git - permanently to https://github.com/OP-TEE/optee_os
(board/beagle/am62_pocketbeagle2: line  145) redirect  https://www.linux-automation.com/en/products/usb-sd-mux.html - with Found to https://linux-automation.com/en/products/usb-sd-mux.html
(board/beagle/am62_pocketbeagle2: line  146) timeout   https://wiki.tizen.org/SDWire - HTTPSConnectionPool(host='wiki.tizen.org', port=443): Max retries exceeded with url: /SDWire (Caused by ConnectTimeoutError(<HTTPSConnection(host='wiki.tizen.org', port=443) at 0x7fd0c271ad50>, 'Connection to wiki.tizen.org timed out. (connect timeout=30)'))
(board/beagle/am62_pocketbeagle2: line    3) broken    https://github.com/openocd-org/openocd/blob/master/tcl/target/ti_k3.cfg#L59 - 404 Client Error: Not Found for url: https://github.com/openocd-org/openocd/blob/master/tcl/target/ti_k3.cfg
(board/beagle/am62x_beagleplay: line   19) redirect  https://beagleplay.org/ - with Found to https://www.beagleboard.org/boards/beagleplay
(board/beagle/am67a_beagley_ai: line   19) redirect  https://beagley-ai.org/ - with Found to https://www.beagleboard.org/boards/beagley-ai
(board/beagle/j721e_beagleboneai64: line   22) redirect  https://beagleboard.org/ai-64 - permanently to https://www.beagleboard.org/boards/beaglebone-ai-64
(board/beagle/j721e_beagleboneai64: line  251) redirect  https://beagleboard.org/ai-64/ - permanently to https://www.beagleboard.org/boards/beaglebone-ai-64
(board/broadcom/bcm7xxx: line   82) broken    https://github.com/Broadcom/stblinux-3.14 - 404 Client Error: Not Found for url: https://github.com/Broadcom/stblinux-3.14
(board/broadcom/bcm7xxx: line   83) broken    https://github.com/Broadcom/stblinux-4.1 - 404 Client Error: Not Found for url: https://github.com/Broadcom/stblinux-4.1
(board/broadcom/bcm7xxx: line   84) broken    https://github.com/Broadcom/stblinux-4.9 - 404 Client Error: Not Found for url: https://github.com/Broadcom/stblinux-4.9
(board/bsh/imx6ulz_bsh_smm_m2: line    8) redirect  https://github.com/NXPmicro/mfgtools - permanently to https://github.com/nxp-imx/mfgtools
(board/canaan/k230_canmv: line   46) redirect  https://kendryte-download.canaan-creative.com/developer/k230/CanMV-K230_debian_sdcard_sdk_1.3.img.gz - permanently to https://download.kendryte.com/developer/k230/CanMV-K230_debian_sdcard_sdk_1.3.img.gz
(board/emulation/qemu-arm: line  255) redirect  https://github.com/stefanberger/swtpm.git - permanently to https://github.com/stefanberger/swtpm
(board/emulation/qemu-riscv: line   84) redirect  https://github.com/riscv/opensbi/blob/master/docs/platform/qemu_virt.md - permanently to https://github.com/riscv-software-src/opensbi/blob/master/docs/platform/qemu_virt.md
(board/emulation/qemu-riscv: line   84) redirect  https://github.com/riscv/opensbi/blob/master/docs/platform/spike.md - permanently to https://github.com/riscv-software-src/opensbi/blob/master/docs/platform/spike.md
(board/google/chromebook_coral: line  442) broken    https://www.coreboot.org/images/2/23/Apollolake_SoC.pdf - 404 Client Error: Not Found for url: https://www.coreboot.org/images/2/23/Apollolake_SoC.pdf
(board/google/chromebook_link: line   25) broken    http://www.coreboot.org/~stepan/pci8086,0166.rom - 404 Client Error: Not Found for url: https://www.coreboot.org/~stepan/pci8086,0166.rom
(board/hisilicon/hikey960: line  118) broken    telnet:0:/dev/ttyUSB0:115200 - 
(board/hisilicon/hikey960: line   97) redirect  https://github.com/TrustedFirmware-A/trusted-firmware-a/blob/master/docs/plat/hikey960.rst - with Found to https://github.com/TrustedFirmware-A/trusted-firmware-a/blob/main/docs/plat/hikey960.rst
(board/hisilicon/hikey: line  116) redirect  https://github.com/TrustedFirmware-A/trusted-firmware-a/blob/master/docs/plat/hikey.rst - with Found to https://github.com/TrustedFirmware-A/trusted-firmware-a/blob/main/docs/plat/hikey.rst
(board/hisilicon/poplar: line   47) redirect  https://github.com/Linaro/poplar-l-loader.git - permanently to https://github.com/Linaro/poplar-l-loader
(board/hisilicon/poplar: line   61) redirect  https://github.com/Linaro/poplar-arm-trusted-firmware.git - permanently to https://github.com/Linaro/poplar-arm-trusted-firmware
(board/intel/crownbay: line   31) broken    http://www.intel.com/content/www/us/en/secure/intelligent-systems/privileged/e6xx-35-b1-cmc22211.html - 403 Client Error: Forbidden for url: https://www.intel.com/content/www/us/en/secure/intelligent-systems/privileged/e6xx-35-b1-cmc22211.html
(board/intel/crownbay: line   31) redirect  http://www.ami.com/products/bios-uefi-tools-and-utilities/bios-uefi-utilities/ - permanently to https://www.ami.com/products/aptio-v/
(board/intel/crownbay: line    7) broken    http://www.intel.com/content/www/us/en/embedded/design-tools/evaluation-platforms/atom-e660-eg20t-development-kit.html - 403 Client Error: Forbidden for url: https://www.intel.com/content/www/us/en/embedded/design-tools/evaluation-platforms/atom-e660-eg20t-development-kit.html
(board/intel/crownbay: line    7) broken    http://www.intel.com/fsp - 403 Client Error: Forbidden for url: https://www.intel.com/fsp
(board/intel/edison: line   58) redirect  https://drive.google.com/drive/u/0/folders/1URPHrOk9-UBsh8hjv-7WwC0W6Fy61uAJ - with Found to https://drive.google.com/drive/folders/1URPHrOk9-UBsh8hjv-7WwC0W6Fy61uAJ
(board/intel/minnowmax: line   21) broken    http://firmware.intel.com/sites/default/files/2014-WW42.4-MinnowBoardMax.73-64-bit.bin_Release.zip - 403 Client Error: Forbidden for url: https://corpredirect.intel.com/Redirector/404Redirector.aspx?https://firmware.intel.com/sites/default/files/2014-WW42.4-MinnowBoardMax.73-64-bit.bin_Release.zip
(board/intel/slimbootloader: line   92) broken    http://downloads.yoctoproject.org/releases/yocto/yocto-2.0/machines/leafhill/ - 404 Client Error: Not Found for url: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0/machines/leafhill/
(board/kontron/osm-s-mx8mp: line  104) redirect  https://docs.kontron-electronics.de - permanently to https://docs.kontron-electronics.de/sw/ked/docs/docs/
(board/microchip/mpfs_common: line  271) broken    https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/boards/mpfs-icicle-kit-es/updating-icicle-kit/updating-icicle-kit-design-and-linux.md - 404 Client Error: Not Found for url: https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/boards/mpfs-icicle-kit-es/updating-icicle-kit/updating-icicle-kit-design-and-linux.md
(board/microchip/mpfs_common: line   29) broken    https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/software-development/hss-payloads.md - 404 Client Error: Not Found for url: https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/software-development/hss-payloads.md
(board/microchip/mpfs_common: line   36) broken    https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/boards/mpfs-icicle-kit-es/updating-icicle-kit/updating-icicle-kit-design-and-linux.md#eMMC - 404 Client Error: Not Found for url: https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/boards/mpfs-icicle-kit-es/updating-icicle-kit/updating-icicle-kit-design-and-linux.md
(board/nxp/mx6ullevk: line   45) broken    https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-development-boards/evaluation-kit-for-the-i-mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK - 404 Client Error: Not Found for url: https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-development-boards/evaluation-kit-for-the-i-mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK
(board/phytec/phycore-am62ax: line   12) redirect  https://www.phytec.com/product/phyboard-am62a - permanently to https://www.phytec.com/product/phyboard-am62a-development-kit/
(board/qualcomm/dragonwing: line    7) redirect  https://docs.qualcomm.com/bundle/publicresource/87-83838-1_REV_A_Qualcomm_IQ6_Series_Product_Brief.pdf - with Found to https://docs.qualcomm.com/doc/87-83838-1/87-83838-1_REV_A_Qualcomm_IQ6_Series_Product_Brief.pdf
(board/qualcomm/dragonwing: line    7) redirect  https://docs.qualcomm.com/bundle/publicresource/87-83839-1_REV_A_Qualcomm_IQ8_Series_Product_Brief________.pdf - with Found to https://docs.qualcomm.com/doc/87-83839-1/87-83839-1_REV_A_Qualcomm_IQ8_Series_Product_Brief________.pdf
(board/qualcomm/dragonwing: line    7) redirect  https://docs.qualcomm.com/bundle/publicresource/87-83840-1_REV_A_Qualcomm_IQ9_Series_Product_Brief.pdf - with Found to https://docs.qualcomm.com/doc/87-83840-1/87-83840-1_REV_A_Qualcomm_IQ9_Series_Product_Brief.pdf
(board/renesas/rcar-gen3-install: line   27) broken    https://github.com/renesas-rcar/flash_writer/blob/rcar_gen3/docs/application-note.md#341-write-to-the-s-record-format-images-to-the-serial-flash - Anchor '341-write-to-the-s-record-format-images-to-the-serial-flash' not found
(board/samsung/e850-96: line 1053) redirect  https://gitlab.com/LinaroLtd/e850-96/images.git - with Found to https://gitlab.com/LinaroLtd/e850-96/images
(board/samsung/e850-96: line 1054) redirect  https://gitlab.com/LinaroLtd/e850-96/tools/dltool.git - with Found to https://gitlab.com/LinaroLtd/e850-96/tools/dltool
(board/samsung/e850-96: line 1059) timeout   https://source.devboardsforandroid.linaro.org/platform/external/u-boot/+log/refs/heads/wip/sm8x50-gbl-fastboot - HTTPSConnectionPool(host='source.devboardsforandroid.linaro.org', port=443): Max retries exceeded with url: /platform/external/u-boot/+log/refs/heads/wip/sm8x50-gbl-fastboot (Caused by ConnectTimeoutError(<HTTPSConnection(host='source.devboardsforandroid.linaro.org', port=443) at 0x7fd0bd90c050>, 'Connection to source.devboardsforandroid.linaro.org timed out. (connect timeout=30)'))
(board/samsung/e850-96: line 1061) timeout   https://source.devboardsforandroid.linaro.org/platform/manifest/ - HTTPSConnectionPool(host='source.devboardsforandroid.linaro.org', port=443): Max retries exceeded with url: /platform/manifest/ (Caused by ConnectTimeoutError(<HTTPSConnection(host='source.devboardsforandroid.linaro.org', port=443) at 0x7fd0bd90e350>, 'Connection to source.devboardsforandroid.linaro.org timed out. (connect timeout=30)'))
(board/schneider/hmibsc: line    7) broken    https://www.se.com/us/en/product/HMIBSCEA53D1L0T/iiot-edge-box-core-harmony-ipc-emmc-dc-linux-tpm/ - 403 Client Error: Forbidden for url: https://www.se.com/us/en/product/HMIBSCEA53D1L0T/iiot-edge-box-core-harmony-ipc-emmc-dc-linux-tpm/
(board/sifive/unleashed: line   55) redirect  https://github.com/riscv/opensbi.git - permanently to https://github.com/riscv-software-src/opensbi
(board/sipeed/maix: line   21) redirect  https://kendryte.com/downloads/ - permanently to https://www.kendryte.com/downloads/
(board/sipeed/maix: line  696) redirect  https://github.com/riscv/riscv-sbi-doc - permanently to https://github.com/riscv-non-isa/riscv-sbi-doc
(board/spacemit/bananapi-f3: line   39) broken    https://bianbu-linux.spacemit.com/en/device/boot#21-firmware-layout - Anchor '21-firmware-layout' not found
(board/starfive/deepcomputing_fml13v01: line   28) broken    https://www.starfivetech.com/uploads/u74mc_core_complex_manual_21G1.pdf - 404 Client Error: Not Found for url: https://www.starfivetech.com/uploads/u74mc_core_complex_manual_21G1.pdf
(board/st/stm32_MCU: line   26) timeout   https://www.st.com/en/microcontrollers-microprocessors/stm32f4-series.html - HTTPSConnectionPool(host='www.st.com', port=443): Read timed out. (read timeout=30)
(board/st/stm32_MCU: line   27) timeout   https://www.st.com/en/microcontrollers-microprocessors/stm32f7-series.html - HTTPSConnectionPool(host='www.st.com', port=443): Read timed out. (read timeout=30)
(board/st/stm32_MCU: line   28) timeout   https://www.st.com/en/microcontrollers-microprocessors/stm32h7-series.html - HTTPSConnectionPool(host='www.st.com', port=443): Read timed out. (read timeout=30)
(board/st/stm32mp1: line  839) timeout   https://wiki.st.com/ - HTTPSConnectionPool(host='wiki.st.com', port=443): Read timed out. (read timeout=30)
(board/st/stm32mp1: line  840) timeout   https://wiki.st.com/stm32mpu/wiki/Main_Page - HTTPSConnectionPool(host='wiki.st.com', port=443): Read timed out. (read timeout=30)
(board/ti/am335x_evm: line   62) redirect  https://www.ti.com/mysecuresoftware - with Found to https://www.ti.com/en-us404.html
(board/ti/am6254atl_sk: line   13) redirect  https://www.ti.com/lit/pdf/spruiv7 - with Found to https://www.ti.com/lit/ug/spruiv7c/spruiv7c.pdf?ts=1787607945585
(board/ti/am62ax_sk: line   39) redirect  https://www.ti.com/lit/pdf/spruj16 - with Found to https://www.ti.com/lit/ug/spruj16c/spruj16c.pdf?ts=1787666228238&ref_url=https%253A%252F%252Fwww.google.com%252F
(board/ti/am62ax_sk: line   71) -ignored- https://git.ti.com/cgit/security-development-tools/core-secdev-k3: service unavailable
(board/ti/am62dx_evm: line   50) redirect  https://www.ti.com/lit/pdf/sprujd4 - with Found to https://www.ti.com/lit/ug/sprujd4a/sprujd4a.pdf?ts=1787675383080
(board/ti/am62px_sk: line   49) redirect  https://www.ti.com/lit/pdf/spruj83 - with Found to https://www.ti.com/lit/ug/spruj83d/spruj83d.pdf?ts=1787675382783
(board/ti/am64x_evm: line   27) redirect  https://www.ti.com/lit/pdf/spruim2 - with Found to https://www.ti.com/lit/ug/spruim2j/spruim2j.pdf?ts=1787675380084
(board/ti/am65x_evm: line   25) redirect  https://www.ti.com/lit/pdf/spruid7 - with Found to https://www.ti.com/lit/ug/spruid7e/spruid7e.pdf?ts=1787675379324
(board/ti/am65x_evm: line   29) broken    https://www.ti.com/tool/TMDX654GPEVM - 404 Client Error: Not Found for url: https://www.ti.com/tool/TMDX654GPEVM
(board/ti/j7200_evm: line   27) redirect  https://www.ti.com/lit/pdf/spruiu1 - with Found to https://www.ti.com/lit/ug/spruiu1d/spruiu1d.pdf?ts=1787675380744
(board/ti/j721e_evm: line   30) redirect  https://www.ti.com/lit/pdf/spruil1 - with Found to https://www.ti.com/lit/ug/spruil1d/spruil1d.zip?ts=1787675380782
(board/ti/j721s2_evm: line   16) redirect  https://www.lauterbach.com/ad3780.html - with Found to https://repo.lauterbach.com/ad3780.html
(board/ti/j721s2_evm: line   23) broken    https://software-dl.ti.com/ccs/esd/xdsdebugprobes/emu_JTAG_connectors.html - 404 Client Error: Not Found for url: https://software-dl.ti.com/ccs/esd/xdsdebugprobes/emu_JTAG_connectors.html
(board/ti/j721s2_evm: line  259) redirect  https://www.ti.com/lit/pdf/spruj68 - with Found to https://www.ti.com/lit/ug/spruj68a/spruj68a.pdf?ts=1787675382134
(board/ti/j721s2_evm: line   33) redirect  https://www.ti.com/lit/pdf/spruj28 - with Found to https://www.ti.com/lit/ug/spruj28f/spruj28f.zip?ts=1787608802464
(board/ti/j721s2_evm: line    3) broken    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_JTAG_connectors.html#cti-20-pin-header-information - 404 Client Error: Not Found for url: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_JTAG_connectors.html
(board/ti/j722s_evm: line   26) redirect  https://www.ti.com/lit/zip/sprujb3 - with Found to https://www.ti.com/lit/ug/sprujb3c/sprujb3c.zip?ts=1787662792674
(board/ti/j784s4_evm: line  311) redirect  https://www.ti.com/lit/ug/spruj70/spruj70.pdf - with Found to https://www.ti.com/lit/ug/spruj70b/spruj70b.pdf?ts=1787675383450
(board/ti/j784s4_evm: line   33) redirect  http://www.ti.com/lit/zip/spruj52 - with Found to https://www.ti.com/lit/ug/spruj52e/spruj52e.zip?ts=1787599944317
(     board/ti/k3: line 1241) redirect  https://sourceware.org/gdb/onlinedocs/gdb/TUI-Commands.html - permanently to https://sourceware.org/gdb/current/onlinedocs/gdb.html/TUI-Commands.html
(     board/ti/k3: line 1333) broken    https://github.com/OP-TEE/optee_ftpm#building-the-ta - Anchor 'building-the-ta' not found
(     board/ti/k3: line  663) redirect  https://dev.ti.com/sysconfig - with Found to https://www.ti.com/en-us404.html
(board/ti/ks2_evm: line  136) broken    http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Getting_Started#Installing_Code_Composer_Studio - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Getting_Started
(board/ti/ks2_evm: line   13) broken    http://www.advantech.com/Support/TI-EVM/EVMK2HX_sd.aspx - 404 Client Error: Not Found for url: https://www.advantech.com/en/errors/page-not-found
(board/ti/ks2_evm: line  141) broken    http://processors.wiki.ti.com/index.php/EVMK2H_Hardware_Setup - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/EVMK2H_Hardware_Setup
(board/ti/ks2_evm: line  142) broken    http://processors.wiki.ti.com/index.php/EVMK2E_Hardware_Setup - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/EVMK2E_Hardware_Setup
(board/ti/ks2_evm: line  143) broken    http://processors.wiki.ti.com/index.php/TCIEVMK2L_Hardware_Setup - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/TCIEVMK2L_Hardware_Setup
(board/ti/ks2_evm: line  144) broken    http://processors.wiki.ti.com/index.php/66AK2G02_GP_EVM_Hardware_Setup - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/66AK2G02_GP_EVM_Hardware_Setup
(board/ti/ks2_evm: line   14) broken    https://www.einfochips.com/index.php/partnerships/texas-instruments/k2e-evm.html - 403 Client Error: Forbidden for url: https://www.einfochips.com/index.php/partnerships/texas-instruments/k2e-evm.html
(board/ti/ks2_evm: line  152) broken    http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Loading_and_Running_U-Boot_on_EVM_through_CCS - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring
(board/ti/ks2_evm: line   15) broken    https://www.einfochips.com/index.php/partnerships/texas-instruments/k2l-evm.html - 403 Client Error: Forbidden for url: https://www.einfochips.com/index.php/partnerships/texas-instruments/k2l-evm.html
(board/ti/ks2_evm: line  208) broken    http://processors.wiki.ti.com/index.php/*_Hardware_Setup - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/*_Hardware_Setup
(board/ti/ks2_evm: line   20) broken    https://www.ti.com/product/tci6638k2h - 404 Client Error: Not Found for url: https://www.ti.com/product/TCI6638K2H
(board/ti/ks2_evm: line   20) broken    https://www.ti.com/product/tci6638k2k - 404 Client Error: Not Found for url: https://www.ti.com/product/TCI6638K2K
(board/ti/ks2_evm: line  235) broken    http://processors.wiki.ti.com/index.php/ - 421 Client Error: Misdirected Request for url: https://processors.wiki.ti.com/index.php/
(board/ti/ks2_evm: line   27) broken    https://www.ti.com/lit/ds/symlink/tci6630k2l.pdf - 404 Client Error: Not Found for url: https://www.ti.com/lit/ds/symlink/tci6630k2l.pdf
(board/ti/ks2_evm: line   30) broken    https://www.ti.com/lit/ds/symlink/66ak2g02.pdf - 404 Client Error: Not Found for url: https://www.ti.com/lit/ds/symlink/66ak2g02.pdf
(board/toradex/aquila-am69: line   22) broken    https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads - 403 Client Error: Forbidden for url: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
(board/toradex/aquila-am69: line   24) redirect  https://developer.arm.com/-/media/Files/downloads/gnu/11.3.rel1/binrel/arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz - with Found to https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu/11.3.rel1/binrel/arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz
(board/toradex/aquila-am69: line   25) redirect  https://developer.arm.com/-/media/Files/downloads/gnu/11.3.rel1/binrel/arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz - with Found to https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu/11.3.rel1/binrel/arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz
(board/toradex/aquila-imx95: line   26) redirect  https://developer.arm.com/-/media/Files/downloads/gnu/14.3.rel1/binrel/arm-gnu-toolchain-14.3.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz - with Found to https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu/14.3.rel1/binrel/arm-gnu-toolchain-14.3.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz
(board/toradex/aquila-imx95: line   27) redirect  https://developer.arm.com/-/media/Files/downloads/gnu/14.3.rel1/binrel/arm-gnu-toolchain-14.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz - with Found to https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu/14.3.rel1/binrel/arm-gnu-toolchain-14.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz
(board/toradex/colibri_imx7: line   32) broken    https://www.nxp.com/webapp/Download?colCode=IMX7DRM - 404 Client Error: Not Found for url: https://www.nxp.com/webapp/Download?colCode=IMX7DRM
(board/toradex/colibri_imx7: line   44) broken    https://www.nxp.com/docs/en/application-note/AN4581.pdf - 404 Client Error: Not Found for url: https://www.nxp.com/docs/en/application-note/AN4581.pdf
(board/toradex/colibri_vf: line    7) broken    https://www.toradex.com/computer-on-modules/colibri-arm-family/nxp-vybrid-vf5xx-vf6xx - 404 Client Error: Not Found for url: https://www.toradex.com/computer-on-modules/colibri-arm-family/nxp-vybrid-vf5xx-vf6xx
(board/xen/xenguest_arm64: line   83) broken    https://source.codeaurora.org/external/imx/uboot-imx/tree/?h=imx_v2018.03_4.14.98_2.0.0_ga - HTTPSConnectionPool(host='source.codeaurora.org', port=443): Max retries exceeded with url: /external/imx/uboot-imx/tree/?h=imx_v2018.03_4.14.98_2.0.0_ga (Caused by NameResolutionError("HTTPSConnection(host='source.codeaurora.org', port=443): Failed to resolve 'source.codeaurora.org' ([Errno -5] No address associated with hostname)"))
(board/xilinx/zynq: line  102) redirect  http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC702-G.htm - permanently to https://www.amd.com/en/products/adaptive-socs-and-fpgas/evaluation-boards.html
(board/xilinx/zynq: line  103) redirect  http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm - permanently to https://www.amd.com/en/products/adaptive-socs-and-fpgas/evaluation-boards.html
(board/xilinx/zynq: line  104) timeout   http://zedboard.org/product/zedboard - HTTPConnectionPool(host='zedboard.org', port=80): Max retries exceeded with url: /product/zedboard (Caused by ConnectTimeoutError(<HTTPConnection(host='zedboard.org', port=80) at 0x7fd0c2252360>, 'Connection to zedboard.org timed out. (connect timeout=30)'))
(board/xilinx/zynq: line  105) timeout   http://zedboard.org/product/microzed - HTTPConnectionPool(host='zedboard.org', port=80): Max retries exceeded with url: /product/microzed (Caused by ConnectTimeoutError(<HTTPConnection(host='zedboard.org', port=80) at 0x7fd0c2252030>, 'Connection to zedboard.org timed out. (connect timeout=30)'))
(board/xilinx/zynq: line  106) redirect  http://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf - with See Other to https://docs.amd.com/r/deeplink/unresolved?ft%3AprettyUrl=en-US%2Fug585-Zynq-7000-TRM
(build/documentation: line   43) redirect  https://docs.u-boot-project.org - with Found to https://docs.u-boot-project.org/en/latest/
(chromium/chainload: line  231) broken    https://www.chromium.org/chromium-os/packages/cros-flashrom - 404 Client Error: Not Found for url: https://www.chromium.org/chromium-os/packages/cros-flashrom
(chromium/chainload: line   29) redirect  https://drive.google.com/open?id=0B7WYZbZ9zd-3dHlVVXo4VXE2T0U - with Found to https://accounts.google.com/v3/signin/identifier?continue=https://drive.google.com/open?id%3D0B7WYZbZ9zd-3dHlVVXo4VXE2T0U&followup=https://drive.google.com/open?id%3D0B7WYZbZ9zd-3dHlVVXo4VXE2T0U&osid=1&passive=1209600&service=wise&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S-231341599:1787675256634161
(chromium/overview: line   54) broken    https://www.cnet.com/products/hp-chromebook-11-g2-11-6-exynos-5250-4-gb-ram-16-gb-emmc/ - 404 Client Error: Not Found for url: https://www.cnet.com/products/hp-chromebook-11-g2-11-6-exynos-5250-4-gb-ram-16-gb-emmc/
(chromium/overview: line   54) broken    https://www.cnet.com/products/samsung-chromebook-2-xe503c12-11-6-exynos-5-octa-4-gb-ram-16-gb-ssd/ - 404 Client Error: Not Found for url: https://www.cnet.com/products/samsung-chromebook-2-xe503c12-11-6-exynos-5-octa-4-gb-ram-16-gb-ssd/
(chromium/overview: line   54) broken    https://www.cnet.com/products/samsung-series-3-chromebook-xe303c12-11-6-exynos-5250-2-gb-ram-16-gb-ssd-bilingual-english-french/ - 404 Client Error: Not Found for url: https://www.cnet.com/products/samsung-series-3-chromebook-xe303c12-11-6-exynos-5250-2-gb-ram-16-gb-ssd-bilingual-english-french/
(develop/bootstd/script: line   27) redirect  https://www.armbian.com - permanently to https://armbian.com/
(develop/ci_testing: line   29) redirect  https://azure.microsoft.com/en-us/services/devops/ - permanently to https://azure.microsoft.com/en-us/products/devops/
(develop/ci_testing: line   43) redirect  https://gitlab.com/ - permanently to https://about.gitlab.com/
(develop/coccinelle: line   78) broken    file:line:column-column - 
(develop/docstyle: line   11) redirect  https://www.sphinx-doc.org - with Found to https://www.sphinx-doc.org/en/master/
(  develop/falcon: line  197) broken    http://schedule2012.rmll.info/IMG/pdf/LSM2012_UbootFalconMode_Babic.pdf - HTTPConnectionPool(host='schedule2012.rmll.info', port=80): Max retries exceeded with url: /IMG/pdf/LSM2012_UbootFalconMode_Babic.pdf (Caused by NewConnectionError("HTTPConnection(host='schedule2012.rmll.info', port=80): Failed to establish a new connection: [Errno 113] No route to host"))
(     develop/gdb: line   64) broken    tcp::3333 - 
(develop/historical/generic_board: line   67) redirect  https://patch.msgid.link/4F019ABB.9010201@gmail.com/ - permanently to https://lore.kernel.org/4F019ABB.9010201@gmail.com/
(develop/historical/generic_board: line   73) redirect  https://patch.msgid.link/CAPnjgZ0jesqX1Y71S5xoYQDGPuARfOX48RGbU9Mw=P5HGYcOKg@mail.gmail.com/ - permanently to https://lore.kernel.org/CAPnjgZ0jesqX1Y71S5xoYQDGPuARfOX48RGbU9Mw=P5HGYcOKg@mail.gmail.com/
(develop/historical/generic_board: line   77) redirect  https://patch.msgid.link/1325477374-6417-1-git-send-email-graeme.russ@gmail.com/ - permanently to https://lore.kernel.org/1325477374-6417-1-git-send-email-graeme.russ@gmail.com/
(develop/package/bintools: line  258) broken    https://www.opendnssec.org/softhsm/ - 404 Client Error: Not Found for url: https://www.opendnssec.org/softhsm/
(develop/package/bintools: line   45) broken    https://www.coreboot.org/CBFS - 404 Client Error: Not Found for url: https://www.coreboot.org/CBFS
(develop/package/entries: line 1830) redirect  https://github.com/riscv/opensbi - permanently to https://github.com/riscv-software-src/opensbi
(develop/package/entries: line 2223) redirect  https://software-dl.ti.com/tisci/esd/latest/ - with Found to https://downloads.ti.com/tisci/esd/latest/
(develop/package/entries: line 3203) broken    https://docs.xilinx.com/r/en-US/ug1283-bootgen-user-guide/Using-Authentication - HTTPSConnectionPool(host='docs.xilinx.com', port=443): Max retries exceeded with url: /r/en-US/ug1283-bootgen-user-guide/Using-Authentication (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1082)')))
(develop/package/entries: line  564) broken    https://uefi.org/sites/default/files/resources/UEFI_Spec_2_10_Aug29.pdf - 403 Client Error: Forbidden for url: https://uefi.org/sites/default/files/resources/UEFI_Spec_2_10_Aug29.pdf
(develop/package/entries: line  611) redirect  https://git.codelinaro.org/linaro/dependable-boot/mbfw/uploads/6f7ddfe3be24e18d4319e108a758d02e/mbfw.pdf - with Found to https://lin-gitlab-gl-prod-gl-uploads-ap-southeast-1-074697959899.s3.ap-southeast-1.amazonaws.com/%40hashed/56/ed/56ed85811d53cda50fa0583c7e3f4fbde02c759b1a0e8fd00d75dd23ffa37631/6f7ddfe3be24e18d4319e108a758d02e/mbfw.pdf?response-content-disposition=inline%3B%20filename%3D%22mbfw.pdf%22%3B%20filename%2A%3DUTF-8%27%27mbfw.pdf&response-content-type=application%2Fpdf&X-Amz-Expires=600&X-Amz-Date=20260825T162739Z&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEEAaDmFwLXNvdXRoZWFzdC0xIkgwRgIhAPMf%2B%2FpQ5kBX2WHs1A0i1vIzBZmgz25mcZpMYy%2FZNOV3AiEA8RInM9%2FK86mf%2F86PqWTCtkAvMVuQGsSZAOePVyypQMMqygUICRACGgwwNzQ2OTc5NTk4OTkiDOJVoyBuvxM2uFN4mCqnBUqLV8UnaWl1mweoxvsLmMbDnlc4hvBFoQ93xCVjFxXoCQDm1JpzcH7pAZrrhOb2F3QL5qJBC4EHFNDIM8mAEWk60JuxeuFOhwIU1%2BOBHkA4zVPeIO1GAXCzRLtkjyDmvUxl%2FHNAjPlV3kdyAAPEYCl5qGp0%2BBrxJsIRC%2FBRCEega5Ti1rpaanUI5RPARP
 qe3OQxbH4SdRo2qmcZsim8SilF%2BtQv5SZCPCBhcZbccaJjPCbApb%2BlfWT9KkspAe3WAscjY5MZYdpk%2Fsd1kx7N6edRWlRux%2FzEgJH9%2FZZsXyic5sZfybcYF86FXk6igO80ClHA6KT%2FLY%2F8F6TG7PrRz9oV0O%2B2gfl%2BFCjpf7oFmwQeldEnNRBn7Zsvz%2FMdncfWqoY9BYVan5esy6isbnZc2JSkTgwW4sDUla3kKA%2Bhp0cqlTgntQPnNDWW0OjZvcAUbKuN%2BZJIKwbM6iLM1yLtqWIRvrMiaDHJbVRMX%2BasSErfbT2%2BhOwqNqn%2FpPBTibXU5Gy30RLZDxlDnVXbzbDlaZSHb20L2LgRJKUE4vAvtyOsvyj48DgelTRX2owIccXHsUdCBMY%2FT8CmFuidmokSTazkfNH0fVseIBOoR41X1Mg9srEDZBG4QccR8ZI8BZV5S7NTtdu1Oi5btgHHRY4Z61FYwWTlYhpuWKZNemtbnXS4%2BkwEZwQQd8me7bKhUIQF5yxkCmfDqkvdPXewtzElY7wp9VBUWcGv1YcYK6jmbGEiWpUbytFX6Qwt86Ah1R6UBCRu%2BHB32QwhaXUfZeBgLSPPG2rAQJ313Mvfud1Yn2b4YFZPMgPM7LBDLdXzagaBNSqqbEt0H4Fozi7aVSr%2F3%2FbOLXAmeb42Bdg0wXPPjbhIvrHU3j3oFWch5kiDd8jHqpXOiY%2BWZ1Qw0ve21AY6sAHae55J5F3KhCZ9%2FU9qfeJe1TP1U5x42JKAw6HKdj54kaM%2FGNTOzeEk9d1z3appMMTYjpKfbAwHd3naNoOD4OSzO2%2F4LuN3XH2Yym0DzgY%2BIaUUFZCXfMXjaA%2FX4iGelwu6P0T614X4aKcbwj5IBFUGTOi9vMoLovIkHEqYew%2B%2B3YEuFCJk8KfhXUyd3bGb5xSlPQHp36zbrfc%2Bw4XdK
 U1da9LwraFlxb1Bum2uJk8u%2BQ%3D%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIARCZCYNHNQN6EK4B7%2F20260825%2Fap-southeast-1%2Fs3%2Faws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=69230228dc66b6cd6bb2d7ade53ef7a76c465bcdd1932c7c3116e019fdd4395d
(develop/python_cq: line   15) redirect  https://www.python.org/dev/peps/pep-0008/ - with Found to https://peps.python.org/pep-0008/
(develop/sending_patches: line  478) broken    https://git.openembedded.org/openembedded/tree/contrib/patchwork/pw-am.sh - 403 Client Error: Forbidden for url: https://git.openembedded.org/openembedded/tree/contrib/patchwork/pw-am.sh
( develop/testing: line   80) redirect  http://www.tbot.tools - permanently to https://tbot.tools/
(develop/uefi/fwu_updates: line  196) broken    https://developer.arm.com/documentation/den0118/ - 403 Client Error: Forbidden for url: https://developer.arm.com/documentation/den0118/
(develop/uefi/u-boot_on_efi: line  376) redirect  http://www.qemu.org - permanently to https://www.qemu.org/
(develop/uefi/u-boot_on_efi: line  377) redirect  https://github.com/tianocore/tianocore.github.io/wiki/OVMF - with Found to https://github.com/tianocore/tianocore.github.io
(develop/uefi/uefi: line 1021) broken    http://uefi.org/specifications - 403 Client Error: Forbidden for url: http://uefi.org/specifications
(develop/uefi/uefi: line 1022) redirect  https://github.com/ARM-software/ebbr/releases/download/v2.1.0/ebbr-v2.1.0.pdf - with Found to https://release-assets.githubusercontent.com/github-production-release-asset/132763627/c53ad724-a4ad-476f-9f1a-df9f6e224906?sp=r&sv=2018-11-09&sr=b&spr=https&se=2026-08-25T17%3A12%3A42Z&rscd=attachment%3B+filename%3Debbr-v2.1.0.pdf&rsct=application%2Foctet-stream&skoid=96c2d410-5711-43a1-aedd-ab1947aa7ab0&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skt=2026-08-25T16%3A12%3A16Z&ske=2026-08-25T17%3A12%3A42Z&sks=b&skv=2018-11-09&sig=Xl6nRtNX2lVx64DUfn3phh2lAk3cg9vbDAAiJMh6Ork%3D&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmVsZWFzZS1hc3NldHMuZ2l0aHVidXNlcmNvbnRlbnQuY29tIiwia2V5Ijoia2V5MSIsImV4cCI6MTc4NzY3NTU2MSwibmJmIjoxNzg3Njc1MjYxLCJwYXRoIjoicmVsZWFzZWFzc2V0cHJvZHVjdGlvbi5ibG9iLmNvcmUud2luZG93cy5uZXQifQ.V57Gd405ZGh-cB_1F5rqZo4eNFWAAjFafbKnWQBxARM&response-content-disposition=attachment%3B%20filename%3Debbr-v2.1.0.pdf&res
 ponse-content-type=application%2Foctet-stream
(develop/uefi/uefi: line 1024) broken    https://developer.arm.com/docs/den0044/latest/server-base-boot-requirements-system-software-on-arm-platforms-version-11 - 403 Client Error: Forbidden for url: https://developer.arm.com/docs/den0044/latest/server-base-boot-requirements-system-software-on-arm-platforms-version-11
(develop/uefi/uefi: line  200) redirect  http://go.microsoft.com/fwlink/?LinkId=321185 - with Found to https://www.microsoft.com/pkiops/certs/MicCorKEKCA2011_2011-06-24.crt
(develop/uefi/uefi: line  202) redirect  http://go.microsoft.com/fwlink/p/?linkid=321192 - permanently to https://www.microsoft.com/pkiops/certs/MicWinProPCA2011_2011-10-19.crt
(develop/uefi/uefi: line  204) redirect  http://go.microsoft.com/fwlink/p/?linkid=321194 - permanently to https://www.microsoft.com/pkiops/certs/MicCorUEFCA2011_2011-06-27.crt
(develop/uefi/uefi: line  694) broken    http://192.168.1.1/foobar - 404 Client Error: Not Found for url: http://192.168.1.1/foobar
(     learn/talks: line   20) broken    https://elinux.org/Boot_Loaders#U-Boot - Anchor 'U-Boot' not found
(  usage/cmd/acpi: line   37) broken    https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf - 403 Client Error: Forbidden for url: https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf
(usage/cmd/meminfo: line  107) broken    https://developer.arm.com/documentation/ddi0487/latest/ - 403 Client Error: Forbidden for url: https://developer.arm.com/documentation/ddi0487/latest/
(  usage/cmd/scmi: line   36) broken    https://developer.arm.com/documentation/den0056/e/?lang=en - 403 Client Error: Forbidden for url: https://developer.arm.com/documentation/den0056/e/?lang=en
(       usage/dfu: line  336) broken    https://dfu-util.sourceforge.net/ - 403 Client Error: Forbidden for url: https://dfu-util.sourceforge.net/
(usage/measured_boot: line   16) broken    https://trustedcomputinggroup.org/resource/pc-client-specific-platform-firmware-profile-specification/ - 403 Client Error: Forbidden for url: https://trustedcomputinggroup.org/resource/pc-client-specific-platform-firmware-profile-specification/
(usage/measured_boot: line   16) broken    https://trustedcomputinggroup.org/resource/tcg-efi-protocol-specification/ - 403 Client Error: Forbidden for url: https://trustedcomputinggroup.org/resource/tcg-efi-protocol-specification/
(usage/semihosting: line   26) broken    http://www.arm.com/products/tools/models/fast-models/foundation-model.php - 403 Client Error: Forbidden for url: https://developer.arm.com/products/system-design/fixed-virtual-platforms
(usage/semihosting: line    7) broken    https://developer.arm.com/documentation/dui0471/g/Semihosting - 403 Client Error: Forbidden for url: https://developer.arm.com/documentation/dui0471/g/Semihosting

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
Quentin Schulz (45):
      doc: arch/mips: update link for Buildroot toolchain
      doc: arch/x86: fix "link" to IRQ router DT binding
      doc: develop: sending_patches: fix links to pw-am.sh
      doc: arch/x86: fix URL to em100
      doc: arch/x86: update link to DediProg SO8 Testclip
      doc: arch/x86: update SFI link
      doc: arch/x86: update MP link
      doc: arch/x86: update link to SeaBIOS
      doc: arch/x86: update link to ACPI
      doc: arch/x86: manual_boot: update links to slides
      doc: develop: uefi: update link to ipxe git repo
      doc: board/amlogic: jethub-j100: update product page
      doc: board/amlogic: jethub-j80: use redirect link directly
      doc: develop: sending_patches: update link to Email Clients and Patches
      doc: develop: sending_patches: update link to GPL license
      doc: usage/pxe: use redirect link
      doc: board/google: chromebook_link: update link to blobs
      doc: arch/sh: remove squatted URL
      doc: develop/coccinelle: update links
      doc: develop/coccinelle: remove dead link in supplemental documentation
      doc: board/nxp: mx6ullevk: replace broken link
      doc: arch/arc: update link
      doc: develop/uefi: stop tripping linkcheck
      doc: board/allwinner: update link to MTD utils
      doc: chromium: update link to Developer Mode
      doc: chromium: update Firmware porting guide link
      doc: chromium: update links to slides
      doc: develop/driver-model: fs_firmware_loader: update link
      doc: board/tbs: update link to TRM
      doc: bootstd: update link to BSL
      doc: learn/talks: remove dead links to slides
      doc: build/gen_compile_commands: update link to point to the right page
      doc: board/highbank: update links to cxmanage and ipmitool tools
      doc: board/siemens: iot2050: update links to files on GitHub
      doc: develop/tests_writing: update links to new GitLab
      doc: board/renesas: update clone instructions to use new GitLab
      doc: fix broken links to mailing lists
      doc: index: update link to mailing list info
      doc: develop/bootstd: fix link to distro_boot
      doc: develop/sending_patches: remove mention to the test mailing list
      doc: chromium/chainload: update instructions on booting on Snow
      doc: develop/sending_patches: use link from ozlabs.org mailman archive
      doc: switch to HTTPS for a few links
      binman: btool: bootgen: update link to user guide
      binman: gbb: update link

 doc/CONTRIBUTE.rst                              |  2 +-
 doc/arch/arc.rst                                |  2 +-
 doc/arch/mips.rst                               |  2 +-
 doc/arch/nios2.rst                              |  2 +-
 doc/arch/sh.rst                                 |  1 -
 doc/arch/x86/manual_boot.rst                    |  4 +--
 doc/arch/x86/x86.rst                            | 20 +++++++--------
 doc/board/allwinner/sunxi.rst                   |  2 +-
 doc/board/amlogic/index.rst                     |  2 +-
 doc/board/amlogic/jethub-j100.rst               |  2 +-
 doc/board/amlogic/jethub-j80.rst                |  2 +-
 doc/board/google/chromebook_link.rst            |  2 +-
 doc/board/highbank/highbank.rst                 |  4 +--
 doc/board/nxp/mx6ullevk.rst                     |  4 +--
 doc/board/renesas/rcar-gen3-draak.rst           |  2 +-
 doc/board/renesas/rcar-gen3-ebisu.rst           |  2 +-
 doc/board/renesas/rcar-gen3-geist.rst           |  2 +-
 doc/board/renesas/rcar-gen3-salvator-x.rst      |  2 +-
 doc/board/renesas/rcar-gen3-ulcb.rst            |  2 +-
 doc/board/renesas/rcar-gen4-sparrow-hawk.rst    |  2 +-
 doc/board/renesas/rcar-gen5-ironhide.rst        |  4 +--
 doc/board/siemens/iot2050.rst                   |  4 +--
 doc/board/sipeed/maix.rst                       |  2 +-
 doc/board/tbs/tbs2910.rst                       |  2 +-
 doc/build/gen_compile_commands.rst              |  2 +-
 doc/chromium/chainload.rst                      |  2 +-
 doc/chromium/overview.rst                       |  8 +++---
 doc/develop/bootstd/overview.rst                |  4 +--
 doc/develop/coccinelle.rst                      | 10 ++------
 doc/develop/driver-model/fs_firmware_loader.rst |  2 +-
 doc/develop/driver-model/virtio.rst             |  2 +-
 doc/develop/process.rst                         |  2 +-
 doc/develop/sending_patches.rst                 | 33 +++++++++++--------------
 doc/develop/tests_writing.rst                   |  4 +--
 doc/develop/uefi/iscsi.rst                      |  6 ++---
 doc/develop/uefi/uefi.rst                       |  2 +-
 doc/index.rst                                   |  2 +-
 doc/learn/talks.rst                             |  3 +--
 doc/usage/dfu.rst                               |  2 +-
 doc/usage/pxe.rst                               |  4 +--
 tools/binman/btool/bootgen.py                   |  2 +-
 tools/binman/etype/gbb.py                       |  2 +-
 42 files changed, 76 insertions(+), 91 deletions(-)
---
base-commit: 2d379a529c257606946831a6dac1c37de6a3f8c0
change-id: 20260824-linkcheck-d7406f22d449

Best regards,
--  
Quentin Schulz <quentin.schulz@cherry.de>

[PATCH next 01/45] doc: arch/mips: update link for Buildroot toolchain

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

http://buildroot.uclibc.org/ redirects to https://buildroot.org so let's
use the final URL directly.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/mips.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/mips.rst b/doc/arch/mips.rst
index aeb58247943a..70d9aa57c389 100644
--- a/doc/arch/mips.rst
+++ b/doc/arch/mips.rst
@@ -8,7 +8,7 @@ Notes for the MIPS architecture port of U-Boot
 Toolchains
 ----------
 
-  * `Buildroot <http://buildroot.uclibc.org/>`_
+  * `Buildroot <https://buildroot.org/>`_
   * `kernel.org cross-development toolchains <https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/>`_
 
 Known Issues

-- 
2.55.0

[PATCH next 02/45] doc: arch/x86: fix "link" to IRQ router DT binding

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The device-tree binding is not part of our Sphinx docs so we cannot
refer to it this way. Instead, follow what we've already done for other
DT bindings and simply use the :download: role.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index f67216d6ce02..066838b956b8 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -242,7 +242,7 @@ debug serial port may be useful here. See setup_internal_uart() for an example.
 During the U-Boot porting, one of the important steps is to write correct PIRQ
 routing information in the board device tree. Without it, device drivers in the
 Linux kernel won't function correctly due to interrupt is not working. Please
-refer to U-Boot `doc <doc/device-tree-bindings/misc/intel,irq-router.txt>`_ for
+refer to :download:`intel,irq-router.txt <../../device-tree-bindings/misc/intel,irq-router.txt>` for
 the device tree bindings of Intel interrupt router. Here we have more details
 on the intel,pirq-routing property below.
 

-- 
2.55.0

[PATCH next 03/45] doc: develop: sending_patches: fix links to pw-am.sh

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The OpenEmbedded wiki doesn't reside at that address (it does at
https://www.openembedded.org/wiki/) but it's unclear what it's useful
for to link to it so instead let's remove the link.

The related pw-am.sh script cannot be found at that address, however it
is available at a new address so let's use that though OE-Core lists it
among the Outdated information in its wiki[1].

[1] https://www.openembedded.org/wiki/Patchwork#Outdated
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/sending_patches.rst | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index 8172dc551838..8286808173d6 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -479,9 +479,8 @@ mbox file and apply it using::
 
    git am file
 
-The `openembedded wiki <http://wiki.openembedded.net/>`_ also provides a script
-named `pw-am.sh
-<http://cgit.openembedded.org/cgit.cgi/openembedded/tree/contrib/patchwork/pw-am.sh>`_
+OpenEmbedded also provides a script named `pw-am.sh
+<https://git.openembedded.org/openembedded/tree/contrib/patchwork/pw-am.sh>`_
 which can be used to fetch an 'mbox' patch from patchwork and git am it::
 
    usage: pw-am.sh <number>

-- 
2.55.0

[PATCH next 04/45] doc: arch/x86: fix URL to em100

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The URL points to nothing on the Coreboot Gerrit. Instead, let's point
at the project page on Gerrit from which one can get the command to use
to clone the repo and also show the changes (patchsets) related to the
project.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 066838b956b8..7abf819e36f4 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -185,7 +185,7 @@ These notes are for those who want to port U-Boot to a new x86 platform.
 Since x86 CPUs boot from SPI flash, a SPI flash emulator is a good investment.
 The Dediprog em100 can be used on Linux.
 
-The em100 tool is available here: http://review.coreboot.org/p/em100.git
+The em100 tool is available here: https://review.coreboot.org/admin/repos/em100,general
 
 On Minnowboard Max the following command line can be used::
 

-- 
2.55.0

[PATCH next 05/45] doc: arch/x86: update link to DediProg SO8 Testclip

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The current link is returning 404. I'm assuming this link here is the
proper product page based on the slug in the URL.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 7abf819e36f4..09d180087fb8 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -192,7 +192,7 @@ On Minnowboard Max the following command line can be used::
    sudo em100 -s -p LOW -d u-boot.rom -c W25Q64DW -r
 
 A suitable clip for connecting over the SPI flash chip is here:
-http://www.dediprog.com/pd/programmer-accessories/EM-TC-8.
+https://www.dediprog.com/product/EM-TC-8.
 
 This allows you to override the SPI flash contents for development purposes.
 Typically you can write to the em100 in around 1200ms, considerably faster

-- 
2.55.0

[PATCH next 06/45] doc: arch/x86: update SFI link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

simplefirmware.org has been redirecting to various different domains
over the past year and those domains don't host anything. Moreover, SFI
was abandoned by the Linux kernel 6 years ago. Let's just point at the
Wikipedia page instead of a non-existing (and possibly domain-squatted)
URL.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 09d180087fb8..3c61c3058f7e 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -483,7 +483,7 @@ TODO List
 .. _coreboot: http://www.coreboot.org
 .. _QEMU: http://www.qemu.org
 .. _microcode: http://en.wikipedia.org/wiki/Microcode
-.. _SFI: http://simplefirmware.org
+.. _SFI: https://en.wikipedia.org/wiki/Simple_Firmware_Interface
 .. _MP: http://www.intel.com/design/archives/processors/pro/docs/242016.htm
 .. _SeaBIOS: http://www.seabios.org/SeaBIOS
 .. _ACPI: http://www.acpi.info

-- 
2.55.0

[PATCH next 07/45] doc: arch/x86: update MP link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The page on the Intel website has been redirecting to a generic page for
the last 10 years according to the wayback machine. Let's just point at
the Wikipedia page instead of some generic and unhelpful URL.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 3c61c3058f7e..e7bd9205caa9 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -484,6 +484,6 @@ TODO List
 .. _QEMU: http://www.qemu.org
 .. _microcode: http://en.wikipedia.org/wiki/Microcode
 .. _SFI: https://en.wikipedia.org/wiki/Simple_Firmware_Interface
-.. _MP: http://www.intel.com/design/archives/processors/pro/docs/242016.htm
+.. _MP: https://en.wikipedia.org/wiki/MultiProcessor_Specification
 .. _SeaBIOS: http://www.seabios.org/SeaBIOS
 .. _ACPI: http://www.acpi.info

-- 
2.55.0

[PATCH next 08/45] doc: arch/x86: update link to SeaBIOS

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

http://www.seabios.org/SeaBIOS returns 404, so let's simply return the
landing page of the documentation instead: https://www.seabios.org/.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index e7bd9205caa9..13d2b2ea9af3 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -485,5 +485,5 @@ TODO List
 .. _microcode: http://en.wikipedia.org/wiki/Microcode
 .. _SFI: https://en.wikipedia.org/wiki/Simple_Firmware_Interface
 .. _MP: https://en.wikipedia.org/wiki/MultiProcessor_Specification
-.. _SeaBIOS: http://www.seabios.org/SeaBIOS
+.. _SeaBIOS: https://www.seabios.org/
 .. _ACPI: http://www.acpi.info

-- 
2.55.0

[PATCH next 09/45] doc: arch/x86: update link to ACPI

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

acpi.info doesn't expose anything anymore.

One of the last archives of that link on the Wayback Machine states[1]
that the ACPI spec is now hosted on uefi.org, so let's update the link
to something that actually is interesting to the user.

[1] https://web.archive.org/web/20190522071820/http://www.acpi.info/
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/x86.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 13d2b2ea9af3..28726f717f6e 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -486,4 +486,4 @@ TODO List
 .. _SFI: https://en.wikipedia.org/wiki/Simple_Firmware_Interface
 .. _MP: https://en.wikipedia.org/wiki/MultiProcessor_Specification
 .. _SeaBIOS: https://www.seabios.org/
-.. _ACPI: http://www.acpi.info
+.. _ACPI: https://uefi.org/acpi/specs

-- 
2.55.0

Re: [PATCH next 09/45] doc: arch/x86: update link to ACPI

[Heinrich Schuchardt]

On 8/25/26 18:49, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> acpi.info doesn't expose anything anymore.
> 
> One of the last archives of that link on the Wayback Machine states[1]
> that the ACPI spec is now hosted on uefi.org, so let's update the link
> to something that actually is interesting to the user.
> 
> [1] https://web.archive.org/web/20190522071820/http://www.acpi.info/
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>   doc/arch/x86/x86.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
> index 13d2b2ea9af3..28726f717f6e 100644
> --- a/doc/arch/x86/x86.rst
> +++ b/doc/arch/x86/x86.rst
> @@ -486,4 +486,4 @@ TODO List
>   .. _SFI: https://en.wikipedia.org/wiki/Simple_Firmware_Interface
>   .. _MP: https://en.wikipedia.org/wiki/MultiProcessor_Specification
>   .. _SeaBIOS: https://www.seabios.org/
> -.. _ACPI: http://www.acpi.info
> +.. _ACPI: https://uefi.org/acpi/specs

This is just a list of outdated ACPI specs.

The current specs are listed at

https://uefi.org/specifications

Best regards

Heinrich

[PATCH next 10/45] doc: arch/x86: manual_boot: update links to slides

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

I'm assuming those are the appropriate links now. linuxfound.org
redirects to linuxfoundation.org. The WHOIS returns the same registrar
(1API GmbH). The Updated Date for linuxfoundation.org and linxfound.org
are 18min apart so I'm assuming they got renewed around the same time.
No guarantee it's the LF that's behind but that'll do for now.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/x86/manual_boot.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/arch/x86/manual_boot.rst b/doc/arch/x86/manual_boot.rst
index 87ebda2e3dd4..649aceef6081 100644
--- a/doc/arch/x86/manual_boot.rst
+++ b/doc/arch/x86/manual_boot.rst
@@ -272,5 +272,5 @@ and change CONFIG_BOOTARGS value in configs/minnowmax_defconfig to::
    CONFIG_BOOTARGS="root=/dev/sda2 ro"
 
 .. _here: https://en.wikipedia.org/wiki/GUID_Partition_Table
-.. _this: http://events.linuxfoundation.org/sites/events/files/slides/chromeos_and_diy_vboot_0.pdf
-.. _that: http://events.linuxfoundation.org/sites/events/files/slides/elce-2014.pdf
+.. _this: http://events.static.linuxfound.org/sites/events/files/slides/chromeos_and_diy_vboot_0.pdf
+.. _that: http://events.static.linuxfound.org/sites/events/files/slides/elce-2014.pdf

-- 
2.55.0

[PATCH next 11/45] doc: develop: uefi: update link to ipxe git repo

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

http://git.ipxe.org/ipxe.git redirects to https://github.com/ipxe/ipxe
so let's use the proper link without a redirect in-between.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/uefi/iscsi.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/uefi/iscsi.rst b/doc/develop/uefi/iscsi.rst
index 51d38cde2438..52fa79f35620 100644
--- a/doc/develop/uefi/iscsi.rst
+++ b/doc/develop/uefi/iscsi.rst
@@ -125,7 +125,7 @@ iPXE
 
 For running iPXE on arm64 the bin-arm64-efi/snp.efi build target is needed::
 
-    git clone http://git.ipxe.org/ipxe.git
+    git clone https://github.com/ipxe/ipxe
     cd ipxe/src
     make bin-arm64-efi/snp.efi -j6 EMBED=myscript.ipxe
 

-- 
2.55.0

Re: [PATCH next 11/45] doc: develop: uefi: update link to ipxe git repo

[Heinrich Schuchardt]

On 8/25/26 18:49, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> http://git.ipxe.org/ipxe.git redirects to https://github.com/ipxe/ipxe
> so let's use the proper link without a redirect in-between.
> 
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>   doc/develop/uefi/iscsi.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/develop/uefi/iscsi.rst b/doc/develop/uefi/iscsi.rst
> index 51d38cde2438..52fa79f35620 100644
> --- a/doc/develop/uefi/iscsi.rst
> +++ b/doc/develop/uefi/iscsi.rst
> @@ -125,7 +125,7 @@ iPXE
>   
>   For running iPXE on arm64 the bin-arm64-efi/snp.efi build target is needed::
>   
> -    git clone http://git.ipxe.org/ipxe.git
> +    git clone https://github.com/ipxe/ipxe

Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>

>       cd ipxe/src
>       make bin-arm64-efi/snp.efi -j6 EMBED=myscript.ipxe
>   
> 

Re: [PATCH next 11/45] doc: develop: uefi: update link to ipxe git repo

[Ilias Apalodimas]

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

On Tue, 25 Aug 2026 at 19:50, Quentin Schulz <foss+uboot@0leil.net> wrote:

> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> http://git.ipxe.org/ipxe.git redirects to https://github.com/ipxe/ipxe
> so let's use the proper link without a redirect in-between.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
>

Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>


> ---
>  doc/develop/uefi/iscsi.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/develop/uefi/iscsi.rst b/doc/develop/uefi/iscsi.rst
> index 51d38cde2438..52fa79f35620 100644
> --- a/doc/develop/uefi/iscsi.rst
> +++ b/doc/develop/uefi/iscsi.rst
> @@ -125,7 +125,7 @@ iPXE
>
>  For running iPXE on arm64 the bin-arm64-efi/snp.efi build target is
> needed::
>
> -    git clone http://git.ipxe.org/ipxe.git
> +    git clone https://github.com/ipxe/ipxe
>      cd ipxe/src
>      make bin-arm64-efi/snp.efi -j6 EMBED=myscript.ipxe
>
>
> --
> 2.55.0
>
>

[-- Attachment #2: Type: text/html, Size: 2129 bytes --]

Re: [PATCH next 11/45] doc: develop: uefi: update link to ipxe git repo

[Ilias Apalodimas]

On Tue, 25 Aug 2026 at 19:50, Quentin Schulz <foss+uboot@0leil.net> wrote:

> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> http://git.ipxe.org/ipxe.git redirects to https://github.com/ipxe/ipxe
> so let's use the proper link without a redirect in-between.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
>

Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>


> ---
>  doc/develop/uefi/iscsi.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/develop/uefi/iscsi.rst b/doc/develop/uefi/iscsi.rst
> index 51d38cde2438..52fa79f35620 100644
> --- a/doc/develop/uefi/iscsi.rst
> +++ b/doc/develop/uefi/iscsi.rst
> @@ -125,7 +125,7 @@ iPXE
>
>  For running iPXE on arm64 the bin-arm64-efi/snp.efi build target is
> needed::
>
> -    git clone http://git.ipxe.org/ipxe.git
> +    git clone https://github.com/ipxe/ipxe
>      cd ipxe/src
>      make bin-arm64-efi/snp.efi -j6 EMBED=myscript.ipxe
>
>
> --
> 2.55.0
>
>

[PATCH next 12/45] doc: board/amlogic: jethub-j100: update product page

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The original link is 404, replace with one I believe to be correct based
on the info on the product page.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/amlogic/jethub-j100.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/board/amlogic/jethub-j100.rst b/doc/board/amlogic/jethub-j100.rst
index cbf1ea761077..053d5aa57ec7 100644
--- a/doc/board/amlogic/jethub-j100.rst
+++ b/doc/board/amlogic/jethub-j100.rst
@@ -3,7 +3,7 @@
 U-Boot for JetHub J100/J110 (A113X)
 ===================================
 
-JetHome Jethub D1/D1+ (http://jethome.ru/jethub-d1p) is a home automation controller device
+JetHome Jethub D1/D1+ (https://jethome.com/d1p/) is a home automation controller device
 manufactured by JetHome with the following specifications:
 
  - Amlogic A113X (ARM Cortex-A53) quad-core up to 1.5GHz

-- 
2.55.0

Re: [PATCH next 12/45] doc: board/amlogic: jethub-j100: update product page

[Viacheslav]

Hi!

25.08.2026 19:49, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> The original link is 404, replace with one I believe to be correct based
> on the info on the product page.
> 
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>   doc/board/amlogic/jethub-j100.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/board/amlogic/jethub-j100.rst b/doc/board/amlogic/jethub-j100.rst
> index cbf1ea761077..053d5aa57ec7 100644
> --- a/doc/board/amlogic/jethub-j100.rst
> +++ b/doc/board/amlogic/jethub-j100.rst
> @@ -3,7 +3,7 @@
>   U-Boot for JetHub J100/J110 (A113X)
>   ===================================
>   
> -JetHome Jethub D1/D1+ (http://jethome.ru/jethub-d1p) is a home automation controller device
> +JetHome Jethub D1/D1+ (https://jethome.com/d1p/) is a home automation controller device
>   manufactured by JetHome with the following specifications:
>   
>    - Amlogic A113X (ARM Cortex-A53) quad-core up to 1.5GHz
> 

Reviewed-by: Viacheslav Bocharov <v@baodeep.com>

[PATCH next 13/45] doc: board/amlogic: jethub-j80: use redirect link directly

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The product page link redirects permanently to something else, so avoid
the hop by pointing at that link instead.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/amlogic/jethub-j80.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/board/amlogic/jethub-j80.rst b/doc/board/amlogic/jethub-j80.rst
index 9195df690502..c3800f9588aa 100644
--- a/doc/board/amlogic/jethub-j80.rst
+++ b/doc/board/amlogic/jethub-j80.rst
@@ -3,7 +3,7 @@
 U-Boot for JetHub J80 (S905W)
 =============================
 
-JetHome Jethub H1 (http://jethome.ru/jethub-h1) is a home automation controller device
+JetHome Jethub H1 (https://jethome.ru/h1/?variation_id=56) is a home automation controller device
 manufactured by JetHome with the following specifications:
 
  - Amlogic S905W (ARM Cortex-A53) quad-core up to 1.5GHz

-- 
2.55.0

Re: [PATCH next 13/45] doc: board/amlogic: jethub-j80: use redirect link directly

[Viacheslav]

Hi!

25.08.2026 19:49, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> The product page link redirects permanently to something else, so avoid
> the hop by pointing at that link instead.
> 
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>   doc/board/amlogic/jethub-j80.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/board/amlogic/jethub-j80.rst b/doc/board/amlogic/jethub-j80.rst
> index 9195df690502..c3800f9588aa 100644
> --- a/doc/board/amlogic/jethub-j80.rst
> +++ b/doc/board/amlogic/jethub-j80.rst
> @@ -3,7 +3,7 @@
>   U-Boot for JetHub J80 (S905W)
>   =============================
>   
> -JetHome Jethub H1 (http://jethome.ru/jethub-h1) is a home automation controller device
> +JetHome Jethub H1 (https://jethome.ru/h1/?variation_id=56) is a home automation controller device

Please, use https://jethome.com/h1/

>   manufactured by JetHome with the following specifications:
>   
>    - Amlogic S905W (ARM Cortex-A53) quad-core up to 1.5GHz
> 


Thanks,

--

Viacheslav

[PATCH next 14/45] doc: develop: sending_patches: update link to Email Clients and Patches

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The article doesn't exist anymore. On the Wayback machine[1], one can
see that the article merely quotes a patch from the mailing list. It
eventually got merged and moved around a bit and is now residing at the
link in this commit.

[1] https://web.archive.org/web/20120512160209/https://kerneltrap.org/Linux/Email_Clients_and_Patches
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/sending_patches.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index 8286808173d6..3944ca4206a0 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -353,8 +353,8 @@ posted before, look up the old threads, and then manually compare if anything
 has been changed, or what.
 
 If you have problems with your e-mail client, for example because it mangles
-white space or wraps long lines, then please read this article about `Email
-Clients and Patches <http://kerneltrap.org/Linux/Email_Clients_and_Patches>`_.
+white space or wraps long lines, then please read this about `Email
+Clients and Patches <https://docs.kernel.org/process/email-clients.html>`_.
 
 Notes
 -----

-- 
2.55.0

[PATCH next 15/45] doc: develop: sending_patches: update link to GPL license

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The link actually (after a looooooong time) redirects to the GPL-3.0
license which isn't the appropriate license. Instead, point at the
GPL-2.0 page.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/sending_patches.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index 3944ca4206a0..92c34c0669d0 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -361,7 +361,7 @@ Notes
 
 1. U-Boot is Free Software that can redistributed and/or modified under the
    terms of the `GNU General Public License
-   <http://www.fsf.org/licensing/licenses/gpl.html>`_ (GPL). Currently (August
+   <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>`_ (GPL). Currently (August
    2022) version 2 of the GPL applies. Please see :download:`Licensing
    <../../Licenses/README>` for details. To allow that later versions of U-Boot
    may be released under a later version of the GPL, all new code that gets

-- 
2.55.0

Re: [PATCH next 15/45] doc: develop: sending_patches: update link to GPL license

[Heinrich Schuchardt]

On 8/25/26 18:49, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> The link actually (after a looooooong time) redirects to the GPL-3.0
> license which isn't the appropriate license. Instead, point at the
> GPL-2.0 page.
> 
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>   doc/develop/sending_patches.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
> index 3944ca4206a0..92c34c0669d0 100644
> --- a/doc/develop/sending_patches.rst
> +++ b/doc/develop/sending_patches.rst
> @@ -361,7 +361,7 @@ Notes
>   
>   1. U-Boot is Free Software that can redistributed and/or modified under the
>      terms of the `GNU General Public License
> -   <http://www.fsf.org/licensing/licenses/gpl.html>`_ (GPL). Currently (August
> +   <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>`_ (GPL). Currently (August
>      2022) version 2 of the GPL applies. Please see :download:`Licensing
>      <../../Licenses/README>` for details. To allow that later versions of U-Boot
>      may be released under a later version of the GPL, all new code that gets
> 

Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>

[PATCH next 16/45] doc: usage/pxe: use redirect link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

Those links actually redirect to wiki.syslinux.org so let's use those
links directly.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/usage/pxe.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/usage/pxe.rst b/doc/usage/pxe.rst
index 18532f182d5c..523bf9f565eb 100644
--- a/doc/usage/pxe.rst
+++ b/doc/usage/pxe.rst
@@ -30,7 +30,7 @@ Commands
 	try. The order and contents of paths it tries mirrors exactly
 	that of PXELINUX - you can read in more detail about it at:
 
-	http://syslinux.zytor.com/wiki/index.php/Doc/pxelinux
+	https://wiki.syslinux.org/wiki/index.php?title=Doc/pxelinux
 
 ``pxe boot``
         **Syntax:** ``pxe boot [pxefile_addr_r]``
@@ -130,7 +130,7 @@ pxe file format
 ---------------
 
 The pxe file format is nearly a subset of the PXELINUX file format;
-see http://syslinux.zytor.com/wiki/index.php/PXELINUX. It's composed
+see https://wiki.syslinux.org/wiki/index.php?title=PXELINUX. It's composed
 of one line commands - global commands, and commands specific to
 labels. Lines beginning with # are treated as comments. White space
 between and at the beginning of lines is ignored.

-- 
2.55.0

[PATCH next 17/45] doc: board/google: chromebook_link: update link to blobs

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

Update link to one suggested in
https://review.coreboot.org/admin/repos/blobs,general. They point at the
same git repo in the end (checked locally with git clone --depth 1).

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/google/chromebook_link.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/board/google/chromebook_link.rst b/doc/board/google/chromebook_link.rst
index 16080304d6e2..f59fc467332f 100644
--- a/doc/board/google/chromebook_link.rst
+++ b/doc/board/google/chromebook_link.rst
@@ -13,7 +13,7 @@ First, you need the following binary blobs:
 
 You can get these binary blobs by::
 
-   $ git clone http://review.coreboot.org/p/blobs.git
+   $ git clone https://review.coreboot.org/blobs
    $ cd blobs
 
 Find the following files:

-- 
2.55.0

[PATCH next 18/45] doc: arch/sh: remove squatted URL

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The KPIT GNU tools URL redirects to some totally unrelated garbage, so
let's remove it.

The other URL in the git diff is left as-is even though no server
currently answers for that URL.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/sh.rst | 1 -
 1 file changed, 1 deletion(-)

diff --git a/doc/arch/sh.rst b/doc/arch/sh.rst
index 3e3759d68b20..87ccab237c48 100644
--- a/doc/arch/sh.rst
+++ b/doc/arch/sh.rst
@@ -73,7 +73,6 @@ Compiler
 --------
 You can use the following of u-boot to compile.
    - `SuperH Linux Open site <http://www.superh-linux.org/>`_
-   - `KPIT GNU tools <http://www.kpitgnutools.com/>`_
 
 Future
 ------

-- 
2.55.0

[PATCH next 19/45] doc: develop/coccinelle: update links

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The original links often time out. On the Wayback Machine[1], the root
URL is redirected to https://coccinelle.gitlabpages.inria.fr so use that
link directly.

[1] https://web.archive.org/web/20251028230912/http://coccinelle.lip6.fr/
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/coccinelle.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/develop/coccinelle.rst b/doc/develop/coccinelle.rst
index 70274c3f5f5a..54ea8eee0e9c 100644
--- a/doc/develop/coccinelle.rst
+++ b/doc/develop/coccinelle.rst
@@ -34,7 +34,7 @@ of many distributions, e.g. :
 
 Some distribution packages are obsolete and it is recommended
 to use the latest version released from the Coccinelle homepage at
-http://coccinelle.lip6.fr/
+https://coccinelle.gitlabpages.inria.fr/website/
 
 Or from Github at:
 
@@ -66,7 +66,7 @@ The wiki documentation always refers to the linux-next version of the script.
 
 For Semantic Patch Language(SmPL) grammar documentation refer to:
 
-http://coccinelle.lip6.fr/documentation.php
+https://coccinelle.gitlabpages.inria.fr/website/documentation.html
 
 Using Coccinelle on the Linux kernel
 ------------------------------------

-- 
2.55.0

Re: [PATCH next 19/45] doc: develop/coccinelle: update links

[Heinrich Schuchardt]

On 8/25/26 18:49, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> The original links often time out. On the Wayback Machine[1], the root
> URL is redirected to https://coccinelle.gitlabpages.inria.fr so use that
> link directly.
> 
> [1] https://web.archive.org/web/20251028230912/http://coccinelle.lip6.fr/
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>   doc/develop/coccinelle.rst | 4 ++--
> 
> diff --git a/doc/develop/coccinelle.rst b/doc/develop/coccinelle.rst
> index 70274c3f5f5a..54ea8eee0e9c 100644
> --- a/doc/develop/coccinelle.rst
> +++ b/doc/develop/coccinelle.rst
> @@ -34,7 +34,7 @@ of many distributions, e.g. :
>   
>   Some distribution packages are obsolete and it is recommended
>   to use the latest version released from the Coccinelle homepage at
> -http://coccinelle.lip6.fr/
> +https://coccinelle.gitlabpages.inria.fr/website/
>   
>   Or from Github at:
>   
> @@ -66,7 +66,7 @@ The wiki documentation always refers to the linux-next version of the script.
>   
>   For Semantic Patch Language(SmPL) grammar documentation refer to:
>   
> -http://coccinelle.lip6.fr/documentation.php
> +https://coccinelle.gitlabpages.inria.fr/website/documentation.html
>   
>   Using Coccinelle on the Linux kernel
>   ------------------------------------
> 

Hello Quentin,

The page was copied from Linux.

Maybe you want to add your fixes there too to avoid loosing the 
corrections when re-syncing.

Best regards

Heinrich

[PATCH next 20/45] doc: develop/coccinelle: remove dead link in supplemental documentation

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

It redirects to a fancy 404. From a cursory look at the Wayback
machine[1], I don't think it has more than what's already in this file
so simply remove the mention of it.

[1] https://web.archive.org/web/20240915073329/https://bottest.wiki.kernel.org/coccicheck
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/coccinelle.rst | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/doc/develop/coccinelle.rst b/doc/develop/coccinelle.rst
index 54ea8eee0e9c..d0ad803fc7b8 100644
--- a/doc/develop/coccinelle.rst
+++ b/doc/develop/coccinelle.rst
@@ -58,12 +58,6 @@ https://github.com/coccinelle/coccinelle/blob/master/install.txt
 Supplemental documentation
 --------------------------
 
-For supplemental documentation refer to the wiki:
-
-https://bottest.wiki.kernel.org/coccicheck
-
-The wiki documentation always refers to the linux-next version of the script.
-
 For Semantic Patch Language(SmPL) grammar documentation refer to:
 
 https://coccinelle.gitlabpages.inria.fr/website/documentation.html

-- 
2.55.0

[PATCH next 21/45] doc: board/nxp: mx6ullevk: replace broken link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

Having the link split like that doesn't work at all as it inserts a
space in a URL, which isn't possible without being escaped. While at it,
replace with the URL it currently redirects to.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/nxp/mx6ullevk.rst | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/doc/board/nxp/mx6ullevk.rst b/doc/board/nxp/mx6ullevk.rst
index a26248a1e3b5..0a7d2616f583 100644
--- a/doc/board/nxp/mx6ullevk.rst
+++ b/doc/board/nxp/mx6ullevk.rst
@@ -42,6 +42,4 @@ Connect the USB cable between the EVK and the PC for the console.
 Insert the micro SD card in the board, power it up and U-Boot messages should
 come up.
 
-The link for the board: http://www.nxp.com/products/microcontrollers-and- \
-processors/arm-processors/i.mx-applications-processors/i.mx-6-processors/ \
-i.mx6qp/evaluation-kit-for-the-i.mx-6ull-applications-processor:MCIMX6ULL-EVK
+The link for the board: https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-development-boards/evaluation-kit-for-the-i-mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK

-- 
2.55.0

Re: [PATCH next 00/45] doc: fix some issues reported by linkcheck

[Quentin Schulz]

Hi all,

Got rate-limited for 24h by my mail server, I'll send the rest of the 
series Thursday.

Cheers,
Quentin

Re: [PATCH next 00/45] doc: fix some issues reported by linkcheck

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

On Tue, Aug 25, 2026 at 06:49:37PM +0200, Quentin Schulz wrote:

> Saw a dead link and made the mistake of running `make linkcheckdocs`.
> Now I'm knee-deep in it and cannot ignore all the dead and redirected
> links. A day later, I've had enough so this is what I managed to fix in
> that time. There are many URLs still redirecting (could be fine, but
> needs to be individually checked as some big companies have a tendencies
> to redirect to generic pages instead of issuing 404s...) or returning
> 4xx. The issue is that those 4xx also need to be individually checked
> because since the AIpocalypse has started many websites now have web
> crawler protection in place and linkcheck will trigger those and be
> denied access (or be heavily rate limited).
> 
> Please be mindful and only run this script once, save its output and
> work on fixing individual errors without rerunning the script, otherwise
> we would only participate in hammering websites even more (linkcheck
> runs multiple workers in parallel and retries when rate-limited).
> 
> Note that linkcheck doesn't check for links in code-blocks so our
> instructions may point at dead links also.
> 
> At an attempt to avoid tens of people running linkcheck at the same
> time, here's the output sorted and filtered on !ok status:

Thanks for doing this, it is helpful and appreciated.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH next 00/45] doc: fix some issues reported by linkcheck

[Heinrich Schuchardt]

On 8/25/26 18:49, Quentin Schulz wrote:
> Saw a dead link and made the mistake of running `make linkcheckdocs`.
> Now I'm knee-deep in it and cannot ignore all the dead and redirected
> links. A day later, I've had enough so this is what I managed to fix in
> that time. There are many URLs still redirecting (could be fine, but
> needs to be individually checked as some big companies have a tendencies
> to redirect to generic pages instead of issuing 404s...) or returning
> 4xx. The issue is that those 4xx also need to be individually checked
> because since the AIpocalypse has started many websites now have web
> crawler protection in place and linkcheck will trigger those and be
> denied access (or be heavily rate limited).
> 
> Please be mindful and only run this script once, save its output and
> work on fixing individual errors without rerunning the script, otherwise
> we would only participate in hammering websites even more (linkcheck
> runs multiple workers in parallel and retries when rate-limited).
> 
> Note that linkcheck doesn't check for links in code-blocks so our
> instructions may point at dead links also.
> 
> At an attempt to avoid tens of people running linkcheck at the same
> time, here's the output sorted and filtered on !ok status:

Hello Quentin,

in patchwork.ozlabs.org, lore.kernel.org/u-boot, and 
https://lists.u-boot-project.org/ only patches 1 - 21 arrived.

Please, send the rest of the series using

--in-reply-to=20260825-linkcheck-v1-0-ee7573fe3a4a@cherry.de

Best regards

Heinrich

Re: [PATCH next 00/45] doc: fix some issues reported by linkcheck

[Quentin Schulz]

Hi Heinrich,

On 8/27/26 1:03 PM, Heinrich Schuchardt wrote:
> On 8/25/26 18:49, Quentin Schulz wrote:
>> Saw a dead link and made the mistake of running `make linkcheckdocs`.
>> Now I'm knee-deep in it and cannot ignore all the dead and redirected
>> links. A day later, I've had enough so this is what I managed to fix in
>> that time. There are many URLs still redirecting (could be fine, but
>> needs to be individually checked as some big companies have a tendencies
>> to redirect to generic pages instead of issuing 404s...) or returning
>> 4xx. The issue is that those 4xx also need to be individually checked
>> because since the AIpocalypse has started many websites now have web
>> crawler protection in place and linkcheck will trigger those and be
>> denied access (or be heavily rate limited).
>>
>> Please be mindful and only run this script once, save its output and
>> work on fixing individual errors without rerunning the script, otherwise
>> we would only participate in hammering websites even more (linkcheck
>> runs multiple workers in parallel and retries when rate-limited).
>>
>> Note that linkcheck doesn't check for links in code-blocks so our
>> instructions may point at dead links also.
>>
>> At an attempt to avoid tens of people running linkcheck at the same
>> time, here's the output sorted and filtered on !ok status:
> 
> Hello Quentin,
> 
> in patchwork.ozlabs.org, lore.kernel.org/u-boot, and https:// 
> eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.u-boot- 
> project.org%2F&data=05%7C02%7Cquentin.schulz%40cherry.de%7C3c09d2cdb28041d4b5cc08df042aede7%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639234254572323528%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=EVMJd%2FfRl5KHcaDFXZvcck%2F38e8nTUtVCJ61A8CT1Cg%3D&reserved=0 only patches 1 - 21 arrived.
> 

I know, 
https://lists.u-boot-project.org/pipermail/u-boot/2026-August/629812.html 
(for some reason it didn't make it to lore.kernel.org...).

I once again got rate limited for 24h, so the last three patches will 
have to wait for this weekend. I'll likely need to split this in two or 
three for a v2 so I don't get rate-limited in the middle of a series.

> Please, send the rest of the series using
> 
> --in-reply-to=20260825-linkcheck-v1-0-ee7573fe3a4a@cherry.de
> 

Thanks, was wondering how to do that!

Cheers,
Quentin

[PATCH 22/45] doc: arch/arc: update link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

Replace with the link it currently redirects to (it has HTTPS also :) ).

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/arc.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/arch/arc.rst b/doc/arch/arc.rst
index f8e04a34f14e..18556e5d3724 100644
--- a/doc/arch/arc.rst
+++ b/doc/arch/arc.rst
@@ -8,7 +8,7 @@ that SoC designers can optimize for a wide range of uses, from deeply embedded
 to high-performance host applications.
 
 More information on ARC cores avaialble here:
-http://www.synopsys.com/IP/ProcessorIP/ARCProcessors/Pages/default.aspx
+https://mips.com/processor-solutions/arc-processors/
 
 Designers can differentiate their products by using patented configuration
 technology to tailor each ARC processor instance to meet specific performance,

[PATCH 23/45] doc: develop/uefi: stop tripping linkcheck

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

https:// trips linkcheck because it thinks it's supposed to be a link
and is malformed. Instead, simply replace with HTTPS.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/uefi/uefi.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst
index 6fd1db6606db..94ddf6904405 100644
--- a/doc/develop/uefi/uefi.rst
+++ b/doc/develop/uefi/uefi.rst
@@ -703,7 +703,7 @@ We need to preset the "httpserverip" environment variable to proceed the wget::
 UEFI HTTP(s) Boot using lwIP
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Similar to the above U-Boot can do EFI HTTP boot using lwIP. If we combine this
-with Mbed TLS we can also download from https://
+with Mbed TLS we can also download from HTTPS.
 
 HTTP(s) Boot can be activated by specifying::
 

[PATCH 24/45] doc: board/allwinner: update link to MTD utils

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The base URL reports Forbidden access. Removing the www. prefix made it
work (note that using HTTPS returns Forbidden access as well).

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/allwinner/sunxi.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/board/allwinner/sunxi.rst b/doc/board/allwinner/sunxi.rst
index d0c89b956b1e..5c2406d39594 100644
--- a/doc/board/allwinner/sunxi.rst
+++ b/doc/board/allwinner/sunxi.rst
@@ -312,7 +312,7 @@ also be uploaded via FEL, check the Wiki's `FEL page`_ for more details.
 .. _`configs/`: https://github.com/crust-firmware/crust/tree/master/configs
 .. _`crust README`: https://github.com/crust-firmware/crust/blob/master/README.md#building-the-firmware
 .. _`linux-sunxi`: https://linux-sunxi.org
-.. _`MTD utils`: http://www.linux-mtd.infradead.org/
+.. _`MTD utils`: http://linux-mtd.infradead.org/
 .. _`magic binary`: https://github.com/linux-sunxi/sunxi-tools/raw/master/bin/fel-sdboot.sunxi
 .. _`sunxi_fel`: https://github.com/linux-sunxi/sunxi-tools
 .. _`FEL page`: https://linux-sunxi.org/FEL/USBBoot

[PATCH 25/45] doc: chromium: update link to Developer Mode

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The current link just says to click on another link as the resource has
migrated, so simply use that new link instead.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/chromium/overview.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/chromium/overview.rst b/doc/chromium/overview.rst
index 790233cb6688..23f224b30594 100644
--- a/doc/chromium/overview.rst
+++ b/doc/chromium/overview.rst
@@ -13,7 +13,7 @@ available:
    - Running U-Boot from the 'altfw' feature, which is available on selected
      Chromebooks from 2019 onwards (initially Grunt). Press '1' from the
      developer-mode screen to get into U-Boot. See here for details:
-     https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_mode.md
+     https://www.chromium.org/chromium-os/developer-library/guides/device/developer-mode/
 
    - Running U-Boot from the disk partition. This involves signing U-Boot and
      placing it on the disk, for booting as a 'kernel'. See

[PATCH 26/45] doc: chromium: update Firmware porting guide link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

It currently serves a 404. Looking at the Wayback Machine[1], I found a
similar page currently being served. It's probably very outdated by now
but at least it's not a 404 anymore.

[1] https://web.archive.org/web/20230520044331/https://www.chromium.org/chromium-os/firmware-porting-guide/
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/chromium/overview.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/chromium/overview.rst b/doc/chromium/overview.rst
index 23f224b30594..acd9ab8bfcba 100644
--- a/doc/chromium/overview.rst
+++ b/doc/chromium/overview.rst
@@ -71,4 +71,4 @@ Here is some material relevant to Chromium OS verified boot with U-Boot:
 
    - `Chromium OS U-Boot <https://www.chromium.org/developers/u-boot>`_
 
-   - `Firmware porting Guide <https://www.chromium.org/chromium-os/firmware-porting-guide>`_
+   - `Firmware porting Guide <https://www.chromium.org/chromium-os/developer-library/guides/firmware/firmware-porting-guide/>`_

[PATCH 27/45] doc: chromium: update links to slides

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The first link doesn't serve anything anymore and the second doesn't
offer a link to download the slides.

pretalx is the service used by the LF for their CFP and hosting slides
and talk abstracts.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/chromium/overview.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/chromium/overview.rst b/doc/chromium/overview.rst
index acd9ab8bfcba..97e2777691c8 100644
--- a/doc/chromium/overview.rst
+++ b/doc/chromium/overview.rst
@@ -44,7 +44,7 @@ Here is some material relevant to Chromium OS verified boot with U-Boot:
      - Author: Simon Glass
      - Presented at Open Source Firmware Conference 2018, Erlangen
      - Describes the work in progress as at the end of 2018
-     - Slides at `OSFC <https://2018.osfc.io/uploads/talk/paper/26/U-Boot_with_Chrome_OS_and_firmware_packaging.pdf>`_
+     - Slides at `OSFC <https://pretalx.com/media/osfc2018/submissions/YBHYHA/resources/U-Boot_with_Chrome_OS_and_firmware_packaging_Rju11gX.pdf>`_
      - `Youtube video 'OSFC - U-Boot with Chrome OS and firmware packaging' <https://www.youtube.com/watch?v=1jknxUvmwpo>`_
 
    - "Verified Boot in Chrome OS and how to make it work for you"
@@ -57,7 +57,7 @@ Here is some material relevant to Chromium OS verified boot with U-Boot:
        spring (`HP Chromebook 11 <https://www.cnet.com/products/hp-chromebook-11-g2-11-6-exynos-5250-4-gb-ram-16-gb-emmc/>`_)
        and pit/pi (`Samsung Chromebook 2 <https://www.cnet.com/products/samsung-chromebook-2-xe503c12-11-6-exynos-5-octa-4-gb-ram-16-gb-ssd/>`_
        with Exynos 5 Octa 5420 in 2014).
-     - Slides at `Google research <https://research.google/pubs/pub42038/>`_
+     - Slides at `Google research <https://elinux.org/images/0/05/Glass-chromeos_and_diy_vboot_0.pdf>`_
      - `Youtube video 'Verified Boot on Chrome OS and How to do it yourself' <https://www.youtube.com/watch?v=kdpZC9jFzZA>`_
 
    - "Chrome University 2018: Chrome OS Firmware and Verified Boot 201"

[PATCH 28/45] doc: develop/driver-model: fs_firmware_loader: update link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The current link redirects to a generic page on the Intel website.
Looking at the Wayback Machine[1], it really looks like what is
currently exposed in the official kernel docs, so used that instead.

[1] https://web.archive.org/web/20220916014111/https://01.org/linuxgraphics/gfx-docs/drm/driver-api/firmware/index.html
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/driver-model/fs_firmware_loader.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/driver-model/fs_firmware_loader.rst b/doc/develop/driver-model/fs_firmware_loader.rst
index 149b8b436ec3..630daf636f18 100644
--- a/doc/develop/driver-model/fs_firmware_loader.rst
+++ b/doc/develop/driver-model/fs_firmware_loader.rst
@@ -6,7 +6,7 @@ File System Firmware Loader
 
 This is file system firmware loader for U-Boot framework, which has very close
 to some Linux Firmware API. For the details of Linux Firmware API, you can refer
-to https://01.org/linuxgraphics/gfx-docs/drm/driver-api/firmware/index.html.
+to https://docs.kernel.org/driver-api/firmware/index.html.
 
 File system firmware loader can be used to load whatever(firmware, image,
 and binary) from the storage device in file system format into target location

[PATCH 29/45] doc: board/tbs: update link to TRM

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The link to the TRM doesn't exist anymore, so let's replace it with one
that provides the first part of the TRM where the BOOT_CFG is explained.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/tbs/tbs2910.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/board/tbs/tbs2910.rst b/doc/board/tbs/tbs2910.rst
index 9d4be61783ed..4f2838bc9bd8 100644
--- a/doc/board/tbs/tbs2910.rst
+++ b/doc/board/tbs/tbs2910.rst
@@ -187,5 +187,5 @@ Links:
 ------
   - https://www.tbsdtv.com/download/document/tbs2910/TBS2910-Matrix-ARM-mini-PC-SCH_rev2.1.pdf
     - The schematics for the revision 2.1 of the TBS2910 Matrix ARM miniPC.
-  - https://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf - The
+  - https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-6DQ-Reference-Manual-IMX6DQRM-R2-Part-1/ta-p/1115983 - The
     SoC reference manual for additional details on the BOOT_CFG registers.

Re: [PATCH 29/45] doc: board/tbs: update link to TRM

[Soeren Moch]

On 27.08.26 21:52, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> The link to the TRM doesn't exist anymore, so let's replace it with one
> that provides the first part of the TRM where the BOOT_CFG is explained.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Acked-by: Soeren Moch <smoch@web.de>

Thanks,
Soeren
> ---
>   doc/board/tbs/tbs2910.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/board/tbs/tbs2910.rst b/doc/board/tbs/tbs2910.rst
> index 9d4be61783ed..4f2838bc9bd8 100644
> --- a/doc/board/tbs/tbs2910.rst
> +++ b/doc/board/tbs/tbs2910.rst
> @@ -187,5 +187,5 @@ Links:
>   ------
>     - https://www.tbsdtv.com/download/document/tbs2910/TBS2910-Matrix-ARM-mini-PC-SCH_rev2.1.pdf
>       - The schematics for the revision 2.1 of the TBS2910 Matrix ARM miniPC.
> -  - https://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf - The
> +  - https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-6DQ-Reference-Manual-IMX6DQRM-R2-Part-1/ta-p/1115983 - The
>       SoC reference manual for additional details on the BOOT_CFG registers.

[PATCH 30/45] doc: bootstd: update link to BSL

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The link states the current version has moved to
https://systemd.io/BOOT_LOADER_SPECIFICATION/ which itself says it's now
hosted at
https://uapi-group.org/specifications/specs/boot_loader_specification/
so used that link instead of making the user hop through multiple hoops.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/bootstd/overview.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/bootstd/overview.rst b/doc/develop/bootstd/overview.rst
index ec9fafa0fa05..106586f667bb 100644
--- a/doc/develop/bootstd/overview.rst
+++ b/doc/develop/bootstd/overview.rst
@@ -882,7 +882,7 @@ Other ideas:
 
 
 .. _distro_bootcmd: https://github.com/u-boot/u-boot/blob/master/include/config_distro_bootcmd.h
-.. _BootLoaderSpec: http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/
+.. _BootLoaderSpec: https://uapi-group.org/specifications/specs/boot_loader_specification/
 .. _distro_boot: https://github.com/u-boot/u-boot/blob/master/boot/distro.c
 .. _bootflow_h: https://github.com/u-boot/u-boot/blob/master/include/bootflow.h
 .. _migrate_patch: https://patchwork.ozlabs.org/project/uboot/patch/20230727215433.578830-2-sjg@chromium.org/

[PATCH 31/45] doc: learn/talks: remove dead links to slides

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

I couldn't find a link to replace it with.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/learn/talks.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/learn/talks.rst b/doc/learn/talks.rst
index d65e3b92be1a..0eca2daf8034 100644
--- a/doc/learn/talks.rst
+++ b/doc/learn/talks.rst
@@ -8,8 +8,7 @@ learn a bit about U-Boot:
 
 * `Tutorial: Introduction to the Embedded Boot Loader U-boot - Behan Webster,
   Converse in Code <https://www.youtube.com/watch?v=INWghYZH3hI>`__
-  from Embedded Linux Conference 2020
-  (`slides <https://cm.e-ale.org/2020/ELC2020/intro-to-u-boot/intro-to-u-boot-2020.pdf>`__).
+  from Embedded Linux Conference 2020.
 
 * `Recent Advances in U-Boot - Simon Glass, Google Inc.
   <https://www.youtube.com/watch?v=YlJBsVZJkDI>`__

[PATCH 32/45] doc: build/gen_compile_commands: update link to point to the right page

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

linkcheck complained that the anchor doesn't exist anymore. Instead, a
separate page is available so link to that instead.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/build/gen_compile_commands.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/build/gen_compile_commands.rst b/doc/build/gen_compile_commands.rst
index 5eb9e4ccb0aa..e67263eb82f4 100644
--- a/doc/build/gen_compile_commands.rst
+++ b/doc/build/gen_compile_commands.rst
@@ -61,7 +61,7 @@ manage build configurations and code analysis. Some of these IDEs include:
 3. **Qt Creator**: Qt Creator, a popular IDE for Qt development, also
    supports compile_commands.json for C/C++ projects. Instructions on how to
    use this feature can be found at
-   https://doc.qt.io/qtcreator/creator-clang-codemodel.html#using-compilation-databases.
+   https://doc.qt.io/qtcreator/creator-how-to-use-compilation-databases.html
 
 4. **Eclipse CDT**: Eclipse's C/C++ Development Tools (CDT) can be
    configured to use JSON compilation databases for better project management.

[PATCH 33/45] doc: board/highbank: update links to cxmanage and ipmitool tools

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

Both repos on GitHub do not exist anymore. ipmitool is still packaged in
distros and they point at sourceforge as the source, which itself says
development is happening on codeberg now.

For cxmanage, it's unclear where the source code resides as no distro
packages it. There is a cxmanage package on PyPI and they list
maintainers that are also maintainers of pyipmi, so I guess this is good
enough.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/highbank/highbank.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/board/highbank/highbank.rst b/doc/board/highbank/highbank.rst
index 654ef8a02699..21d76436b369 100644
--- a/doc/board/highbank/highbank.rst
+++ b/doc/board/highbank/highbank.rst
@@ -73,6 +73,6 @@ existing U-Boot, and execute it with bootm::
     => tftpboot 0x8000 u-boot-highbank.img
     => bootm
 
-.. _`ipmitool`: https://github.com/Cynerva/ipmitool
+.. _`ipmitool`: https://codeberg.org/IPMITool/ipmitool
 .. _`pyipmi`: https://pypi.org/project/pyipmi/
-.. _`management script`: https://github.com/Cynerva/cxmanage
+.. _`management script`: https://pypi.org/project/cxmanage/

[PATCH 34/45] doc: board/siemens: iot2050: update links to files on GitHub

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The repo got reorganized into multiple layers in commit
https://github.com/siemens/meta-iot2050/commit/db272a3508ed0f0226f6da5bb19e4d21fab55391
so let's update the links to still point at what's intended (hopefully).

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/siemens/iot2050.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/board/siemens/iot2050.rst b/doc/board/siemens/iot2050.rst
index 37b23f6146ba..2c0a324485cc 100644
--- a/doc/board/siemens/iot2050.rst
+++ b/doc/board/siemens/iot2050.rst
@@ -25,7 +25,7 @@ ATF:    Upstream release 2.4 or newer
 OP-TEE: Upstream release 3.10.0 or newer
 
 Binary dependencies can be found in
-https://github.com/siemens/meta-iot2050/tree/master/recipes-bsp/u-boot/files/prebuild.
+https://github.com/siemens/meta-iot2050/tree/master/meta/recipes-bsp/u-boot/files/prebuild.
 The following binaries from that source need to be present in the build folder:
 
  - seboot_pg1.bin
@@ -44,7 +44,7 @@ needs to be present in the build folder:
  - otpcmd.bin
 
 Regarding how to generating this otpcmd.bin, please refer to:
-https://github.com/siemens/meta-iot2050/tree/master/recipes-bsp/secure-boot-otp-provisioning/files/make-otpcmd.sh
+https://github.com/siemens/meta-iot2050/blob/master/meta/recipes-bsp/secure-boot-otp-provisioning/files/make-otpcmd.sh
 
 Building
 --------

[PATCH 35/45] doc: develop/tests_writing: update links to new GitLab

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The GitLab is now hosted at git.u-boot-project.org so let's update those
old links that weren't migrated in the previous relocation from
gitlab.denx.de to source.denx.de.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/tests_writing.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/develop/tests_writing.rst b/doc/develop/tests_writing.rst
index 1a020caa4111..1a6d13f6c7c4 100644
--- a/doc/develop/tests_writing.rst
+++ b/doc/develop/tests_writing.rst
@@ -236,7 +236,7 @@ Include ``test/ut.h`` defines a number of macros to check values and to return
 from the test function if the assertion fails. See :doc:`../api/test`
 for details.
 
-[1] https://gitlab.denx.de/u-boot/u-boot/-/commit/9fe064646d2
+[1] https://git.u-boot-project.org/u-boot/u-boot/-/commit/9fe064646d
 
 
 Add a new driver model test
@@ -282,7 +282,7 @@ implementations work as expected.
 
 Example commit: c48cb7ebfb4 ("sandbox: add ADC unit tests") [1]
 
-[1] https://gitlab.denx.de/u-boot/u-boot/-/commit/c48cb7ebfb4
+[1] https://git.u-boot-project.org/u-boot/u-boot/-/commit/c48cb7ebfb4
 
 
 Add a new test suite

[PATCH 36/45] doc: board/renesas: update clone instructions to use new GitLab

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

While source.denx.de still resolves at the moment, it's not guaranteed
it'll do so forever. So migrate the instructions to the new GitLab at
git.u-boot-project.org.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/board/renesas/rcar-gen3-draak.rst        | 2 +-
 doc/board/renesas/rcar-gen3-ebisu.rst        | 2 +-
 doc/board/renesas/rcar-gen3-geist.rst        | 2 +-
 doc/board/renesas/rcar-gen3-salvator-x.rst   | 2 +-
 doc/board/renesas/rcar-gen3-ulcb.rst         | 2 +-
 doc/board/renesas/rcar-gen4-sparrow-hawk.rst | 2 +-
 doc/board/renesas/rcar-gen5-ironhide.rst     | 4 ++--
 7 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/board/renesas/rcar-gen3-draak.rst b/doc/board/renesas/rcar-gen3-draak.rst
index 7b94eaa4b237..061ecd05291a 100644
--- a/doc/board/renesas/rcar-gen3-draak.rst
+++ b/doc/board/renesas/rcar-gen3-draak.rst
@@ -16,7 +16,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
diff --git a/doc/board/renesas/rcar-gen3-ebisu.rst b/doc/board/renesas/rcar-gen3-ebisu.rst
index f9632705abcf..a41f736a767f 100644
--- a/doc/board/renesas/rcar-gen3-ebisu.rst
+++ b/doc/board/renesas/rcar-gen3-ebisu.rst
@@ -16,7 +16,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
diff --git a/doc/board/renesas/rcar-gen3-geist.rst b/doc/board/renesas/rcar-gen3-geist.rst
index 7bedb3a79cb5..63abb3e22b4d 100644
--- a/doc/board/renesas/rcar-gen3-geist.rst
+++ b/doc/board/renesas/rcar-gen3-geist.rst
@@ -14,7 +14,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
diff --git a/doc/board/renesas/rcar-gen3-salvator-x.rst b/doc/board/renesas/rcar-gen3-salvator-x.rst
index 37f009452e5d..a6ef15a6da40 100644
--- a/doc/board/renesas/rcar-gen3-salvator-x.rst
+++ b/doc/board/renesas/rcar-gen3-salvator-x.rst
@@ -17,7 +17,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
diff --git a/doc/board/renesas/rcar-gen3-ulcb.rst b/doc/board/renesas/rcar-gen3-ulcb.rst
index 88ec2276a366..01e15fa29b67 100644
--- a/doc/board/renesas/rcar-gen3-ulcb.rst
+++ b/doc/board/renesas/rcar-gen3-ulcb.rst
@@ -18,7 +18,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
diff --git a/doc/board/renesas/rcar-gen4-sparrow-hawk.rst b/doc/board/renesas/rcar-gen4-sparrow-hawk.rst
index a1b92ecab57d..af1eb6c6f6f7 100644
--- a/doc/board/renesas/rcar-gen4-sparrow-hawk.rst
+++ b/doc/board/renesas/rcar-gen4-sparrow-hawk.rst
@@ -17,7 +17,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
diff --git a/doc/board/renesas/rcar-gen5-ironhide.rst b/doc/board/renesas/rcar-gen5-ironhide.rst
index 0e775a88f8d6..31a5bb14ae68 100644
--- a/doc/board/renesas/rcar-gen5-ironhide.rst
+++ b/doc/board/renesas/rcar-gen5-ironhide.rst
@@ -22,7 +22,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:
@@ -71,7 +71,7 @@ newly cloned source directory:
 
 .. code-block:: console
 
-    $ git clone https://source.denx.de/u-boot/u-boot.git/
+    $ git clone https://git.u-boot-project.org/u-boot/u-boot.git
     $ cd u-boot
 
 Configure U-Boot:

[PATCH 37/45] doc: fix broken links to mailing lists

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The new domain needs /mailman added after the domain to be able to reach
the mailman information page about the mailing list, so add it.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/CONTRIBUTE.rst              | 2 +-
 doc/develop/sending_patches.rst | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/CONTRIBUTE.rst b/doc/CONTRIBUTE.rst
index c7e5d9656c9a..e03945157029 100644
--- a/doc/CONTRIBUTE.rst
+++ b/doc/CONTRIBUTE.rst
@@ -28,7 +28,7 @@ Contributions
 
 Contributions to the project are welcome. The U-Boot project uses a fairly
 traditional Linux style development work-flow using git and `a mailing list
-<https://lists.u-boot-project.org/listinfo/u-boot>`_.
+<https://lists.u-boot-project.org/mailman/listinfo/u-boot>`_.
 
 Patches should be sent to the mailing list using ``git send-email`` or the
 equivalent commands using ``b4`` or ``patman`` with appropriate sign-off and
diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index 92c34c0669d0..a1e80eaff14c 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -5,7 +5,7 @@ Sending patches
 
 *Before you begin* to implement any new ideas or concepts it is always a good
 idea to present your plans on the `U-Boot mailing list
-<https://lists.u-boot-project.org/listinfo/u-boot>`_. U-Boot supports a huge amount of
+<https://lists.u-boot-project.org/mailman/listinfo/u-boot>`_. U-Boot supports a huge amount of
 very different systems, and it is often impossible for the individual developer
 to oversee the consequences of a specific change to all architectures.
 Discussing concepts early can help you to avoid spending effort on code which,
@@ -87,7 +87,7 @@ General Patch Submission Rules
 ------------------------------
 
 * All patches must be sent to the `u-boot@lists.u-boot-project.org
-  <https://lists.u-boot-project.org/listinfo/u-boot>`_ mailing list.
+  <https://lists.u-boot-project.org/mailman/listinfo/u-boot>`_ mailing list.
 
 * If your patch affects the code maintained by one of the :ref:`custodians`, CC
   them when emailing your patch. The easiest way to make sure you don't forget

[PATCH 38/45] doc: index: update link to mailing list info

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The landing page of mailman with all mailing lists hosted on
lists.u-boot-project.org isn't really useful to the typical user as the
two other lists are for custodians or board maintainers. Therefore,
point at the information page for the most relevant mailing list for
most users.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/index.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/index.rst b/doc/index.rst
index 6fe8ca0788b3..7397baeee0af 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -9,7 +9,7 @@ This is the top level of the U-Boot's documentation tree.  U-Boot
 documentation, like the U-Boot itself, is very much a work in progress;
 that is especially true as we work to integrate our many scattered
 documents into a coherent whole.  Please note that improvements to the
-documentation are welcome; join the U-Boot list at http://lists.u-boot-project.org
+documentation are welcome; join the U-Boot list at https://lists.u-boot-project.org/mailman/listinfo/u-boot
 if you want to help out.
 
 .. toctree::

[PATCH 39/45] doc: develop/bootstd: fix link to distro_boot

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

We never had a file in boot/distro.c. The only time we had a
distro_boot() function was between v2022.07 when it was introduced and
v2023.07 (excluded) when it was renamed to extlinux_boot(). So let's
just point at the latest release that still had it.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/bootstd/overview.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/bootstd/overview.rst b/doc/develop/bootstd/overview.rst
index 106586f667bb..cf8ef419d4b2 100644
--- a/doc/develop/bootstd/overview.rst
+++ b/doc/develop/bootstd/overview.rst
@@ -883,6 +883,6 @@ Other ideas:
 
 .. _distro_bootcmd: https://github.com/u-boot/u-boot/blob/master/include/config_distro_bootcmd.h
 .. _BootLoaderSpec: https://uapi-group.org/specifications/specs/boot_loader_specification/
-.. _distro_boot: https://github.com/u-boot/u-boot/blob/master/boot/distro.c
+.. _distro_boot: https://github.com/u-boot/u-boot/blob/v2023.04/boot/bootmeth_distro.c
 .. _bootflow_h: https://github.com/u-boot/u-boot/blob/master/include/bootflow.h
 .. _migrate_patch: https://patchwork.ozlabs.org/project/uboot/patch/20230727215433.578830-2-sjg@chromium.org/

[PATCH 40/45] doc: develop/sending_patches: remove mention to the test mailing list

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

We don't have one on the new mailman and Tom said[1] it was so rarely
used it doesn't make sense for now to set up one on the new mailman,
thus drop it.

[1] https://libera.catirclogs.org/u-boot/2026-08-25#40371346;
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/sending_patches.rst | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index a1e80eaff14c..ca30c6dde1b6 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -142,10 +142,6 @@ General Patch Submission Rules
   like wrapping of longer lines etc.
   The best way to send patches is by not using your regular mail tool, but by
   using either ``git send-email`` or the ``git imap-send`` command instead.
-  If you believe you need to use a mailing list for testing (instead of any
-  regular mail address you own), we have a special test list for such purposes.
-  It would be best to subscribe to the list for the duration of your tests to
-  avoid repeated moderation - see https://lists.u-boot-project.org/listinfo/test
 
 * Choose a meaningful Subject: - keep in mind that the Subject will also be
   visible as headline of your commit message. Make sure the subject does not

[PATCH 41/45] doc: chromium/chainload: update instructions on booting on Snow

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The link returns a 404 and the Appendix A. link at the bottom of
https://www.chromium.org/chromium-os/developer-library/guides/firmware/firmware-porting-guide
is a dead link. I found this by looking on a web search engine for a
couple seconds and it seems to be matching the title. No clue where this
file is supposed to be exposed so let's point at the file in the git
repo for now.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/chromium/chainload.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/chromium/chainload.rst b/doc/chromium/chainload.rst
index 0f61e020db8d..6f8a134c94bf 100644
--- a/doc/chromium/chainload.rst
+++ b/doc/chromium/chainload.rst
@@ -34,7 +34,7 @@ Snow (Samsung ARM Chromebook)
 
 See here:
 
-https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
+https://chromium.googlesource.com/playground/chromium-org-site/+/refs/heads/main/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook.md
 
 
 Nyan-big

[PATCH 42/45] doc: develop/sending_patches: use link from ozlabs.org mailman archive

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

This avoids triggering checkpatch that asks us to use lore.kernel.org
where the patchwork mailing list isn't hosted.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/develop/sending_patches.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index ca30c6dde1b6..27363a448b23 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -506,4 +506,4 @@ for an overview on how to use it.
 pwparser
 ^^^^^^^^
 
-See http://www.mail-archive.com/patchwork@lists.ozlabs.org/msg00057.html
+See https://lists.ozlabs.org/pipermail/patchwork/2010-January/000186.html

[PATCH 43/45] doc: switch to HTTPS for a few links

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

It's 2026, we really should be using HTTPS wherever possible. The links
in this commit were individually tested, they work fine (the sipeed one
sometimes times out but I'm guessing it's hosted in China and it's not
uncommon for Europeans to have issues reaching servers there).

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 doc/arch/nios2.rst                  |  2 +-
 doc/arch/x86/x86.rst                |  6 +++---
 doc/board/amlogic/index.rst         |  2 +-
 doc/board/sipeed/maix.rst           |  2 +-
 doc/develop/driver-model/virtio.rst |  2 +-
 doc/develop/process.rst             |  2 +-
 doc/develop/sending_patches.rst     | 12 ++++++------
 doc/develop/uefi/iscsi.rst          |  4 ++--
 doc/usage/dfu.rst                   |  2 +-
 9 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/doc/arch/nios2.rst b/doc/arch/nios2.rst
index 90b4ddf387bf..a825b244ab7b 100644
--- a/doc/arch/nios2.rst
+++ b/doc/arch/nios2.rst
@@ -10,7 +10,7 @@ Please refer to the link for more information on Nios II:
 https://www.altera.com/products/processors/overview.html
 
 Please refer to the link for Linux port and toolchains:
-http://rocketboards.org/foswiki/view/Documentation/NiosIILinuxUserManual
+https://rocketboards.org/foswiki/view/Documentation/NiosIILinuxUserManual
 
 The Nios II port of u-boot is controlled by device tree. Please check
 out :doc:`/develop/devicetree/control`.
diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 28726f717f6e..9ba5c2893379 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -480,9 +480,9 @@ TODO List
 - Audio
 - Chrome OS verified boot
 
-.. _coreboot: http://www.coreboot.org
-.. _QEMU: http://www.qemu.org
-.. _microcode: http://en.wikipedia.org/wiki/Microcode
+.. _coreboot: https://www.coreboot.org
+.. _QEMU: https://www.qemu.org
+.. _microcode: https://en.wikipedia.org/wiki/Microcode
 .. _SFI: https://en.wikipedia.org/wiki/Simple_Firmware_Interface
 .. _MP: https://en.wikipedia.org/wiki/MultiProcessor_Specification
 .. _SeaBIOS: https://www.seabios.org/
diff --git a/doc/board/amlogic/index.rst b/doc/board/amlogic/index.rst
index 23380ac33f2b..e8bb421ed8c9 100644
--- a/doc/board/amlogic/index.rst
+++ b/doc/board/amlogic/index.rst
@@ -6,7 +6,7 @@ Amlogic
 Hardware Support Matrix
 -----------------------
 
-An up-do-date matrix is also available on: http://linux-meson.com
+An up-do-date matrix is also available on: https://linux-meson.com
 
 This matrix concerns the actual source code version.
 
diff --git a/doc/board/sipeed/maix.rst b/doc/board/sipeed/maix.rst
index 4568bb3e4b74..9bbc2a93c5b0 100644
--- a/doc/board/sipeed/maix.rst
+++ b/doc/board/sipeed/maix.rst
@@ -19,7 +19,7 @@ Currently, only the Sipeed MAIX BiT V2.0 (bitm) and Sipeed MAIXDUINO are
 supported, but the boards are fairly similar.
 
 Documentation for Maix boards is available from
-`Sipeed's website <http://dl.sipeed.com/MAIX/HDK/>`_.
+`Sipeed's website <https://dl.sipeed.com/MAIX/HDK/>`_.
 Documentation for the Kendryte K210 is available from
 `Kendryte's website <https://kendryte.com/downloads/>`_. However, hardware
 details are rather lacking, so most technical reference has been taken from the
diff --git a/doc/develop/driver-model/virtio.rst b/doc/develop/driver-model/virtio.rst
index 9a5e3240c3ce..e5da9f4301ca 100644
--- a/doc/develop/driver-model/virtio.rst
+++ b/doc/develop/driver-model/virtio.rst
@@ -284,5 +284,5 @@ for the remove method to be called before jumping to OS.
 
 6. do funny stuff with the driver
 
-.. _VirtIO: http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.pdf
+.. _VirtIO: https://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.pdf
 .. _QEMU: https://www.qemu.org
diff --git a/doc/develop/process.rst b/doc/develop/process.rst
index 3c783ed5a0e9..8ade440d84b1 100644
--- a/doc/develop/process.rst
+++ b/doc/develop/process.rst
@@ -236,7 +236,7 @@ Tooling
 
 There are a number of tools available to help custodians and
 contributors alike with their contributions. As a project we make use of
-the Patchwork project hosted at `OzLabs <http://patchwork.ozlabs.org/>`__
+the Patchwork project hosted at `OzLabs <https://patchwork.ozlabs.org/>`__
 and more discussion on how it is used from both a contributor as well as
 custodian point of view can be found :ref:`here <patchwork>`.
 
diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index 27363a448b23..b4f82eb18e16 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -15,7 +15,7 @@ resource - use it. Being familiar with the :doc:`process` is also important.
 
 A good introduction how to prepare for submitting patches can be found in the
 LWN article `How to Get Your Change Into the Linux Kernel
-<http://lwn.net/Articles/139918/>`_ as the same rules apply to U-Boot, too.
+<https://lwn.net/Articles/139918/>`_ as the same rules apply to U-Boot, too.
 
 .. _b4_contrib:
 
@@ -313,7 +313,7 @@ to observe the following rules.
   Note: it is *not* sufficient to provide a change log in some cover letter
   that gets sent as a separate message with the patch series. The reason is
   that such cover letters are not as easily reviewed in our `patchwork queue
-  <http://patchwork.ozlabs.org/project/uboot/list/>`_ so they are not helpful
+  <https://patchwork.ozlabs.org/project/uboot/list/>`_ so they are not helpful
   to any reviewers using this tool. Example::
 
    From: Joe Hacker <jh@hackers.paradise.com>
@@ -380,12 +380,12 @@ Notes
 Patch Tracking
 --------------
 
-Like some other projects, U-Boot uses `Patchwork <http://patchwork.ozlabs.org/>`__
+Like some other projects, U-Boot uses `Patchwork <https://patchwork.ozlabs.org/>`__
 to track the state of patches. This is one of the reasons why it is mandatory
 to submit all patches to the U-Boot mailing list - only then they will be
 picked up by patchwork.
 
-At http://patchwork.ozlabs.org/project/uboot/list/ you can find the list of
+At https://patchwork.ozlabs.org/project/uboot/list/ you can find the list of
 open U-Boot patches. By using the "Filters" link (Note: requires JavaScript)
 you can also select other views, for example, to include old patches that have,
 for example, already been applied or rejected.
@@ -470,7 +470,7 @@ Apply patches
 ^^^^^^^^^^^^^
 
 To apply a patch from the `patchwork queue
-<http://patchwork.ozlabs.org/project/uboot/list/>`_ using ``git``, download the
+<https://patchwork.ozlabs.org/project/uboot/list/>`_ using ``git``, download the
 mbox file and apply it using::
 
    git am file
@@ -495,7 +495,7 @@ The `pwclient` command line tool can be used for example to retrieve patches,
 search the queue or update the state.
 
 All necessary information for `pwclient` is linked from the bottom of
-http://patchwork.ozlabs.org/project/uboot/
+https://patchwork.ozlabs.org/project/uboot/
 
 Use::
 
diff --git a/doc/develop/uefi/iscsi.rst b/doc/develop/uefi/iscsi.rst
index 52fa79f35620..104ef87705fc 100644
--- a/doc/develop/uefi/iscsi.rst
+++ b/doc/develop/uefi/iscsi.rst
@@ -131,11 +131,11 @@ For running iPXE on arm64 the bin-arm64-efi/snp.efi build target is needed::
 
 The available commands for the boot script are documented at:
 
-http://ipxe.org/cmd
+https://ipxe.org/cmd
 
 Credentials are managed as environment variables. These are described here:
 
-http://ipxe.org/cfg
+https://ipxe.org/cfg
 
 iPXE by default will put the CPU to rest when waiting for input. U-Boot does
 not wake it up due to missing interrupt support. To avoid this behavior create
diff --git a/doc/usage/dfu.rst b/doc/usage/dfu.rst
index c825cdcbe5c9..987f287b483e 100644
--- a/doc/usage/dfu.rst
+++ b/doc/usage/dfu.rst
@@ -334,7 +334,7 @@ When U-Boot runs the dfu stack, the DFU host tools can be used
 to send/receive firmware images on each configured alternate.
 
 For example dfu-util is a host side implementation of the DFU 1.1
-specifications(http://dfu-util.sourceforge.net/) which works with U-Boot.
+specifications(https://dfu-util.sourceforge.net/) which works with U-Boot.
 
 Usage
 -----

[PATCH next 44/45] binman: btool: bootgen: update link to user guide

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The link doesn't serve the document anymore. It's available both in HTML
and PDF form at another address but let's point at the HTML version in
hope it stays online longer.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 tools/binman/btool/bootgen.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/binman/btool/bootgen.py b/tools/binman/btool/bootgen.py
index 1bc9f0aa96f3..f740381b7047 100644
--- a/tools/binman/btool/bootgen.py
+++ b/tools/binman/btool/bootgen.py
@@ -7,7 +7,7 @@
 bootgen allows creating bootable SPL for Zynq(MP)
 
 Documentation is available via:
-https://www.xilinx.com/support/documents/sw_manuals/xilinx2022_1/ug1283-bootgen-user-guide.pdf
+https://docs.amd.com/r/en-US/ug1283-bootgen-user-guide/
 
 Source code is available at:
 https://github.com/Xilinx/bootgen

[PATCH next 45/45] binman: gbb: update link

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The current link results in a 404. Looking at the Wayback Machine[1], I
found a similar page currently being served. It's probably very outdated
by now but at least it's not a 404 anymore.

[1] https://web.archive.org/web/20230520044331/https://www.chromium.org/chromium-os/firmware-porting-guide/
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 tools/binman/etype/gbb.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/binman/etype/gbb.py b/tools/binman/etype/gbb.py
index cca18af6e2fa..70067a545047 100644
--- a/tools/binman/etype/gbb.py
+++ b/tools/binman/etype/gbb.py
@@ -48,7 +48,7 @@ class Entry_gbb(Entry):
     the root and recovery keys that are used to verify the boot process. Some
     more details are here:
 
-        https://www.chromium.org/chromium-os/firmware-porting-guide/2-concepts
+        https://www.chromium.org/chromium-os/developer-library/guides/firmware/firmware-porting-guide/2-concepts/
 
     but note that the page dates from 2013 so is quite out of date. See
     README.chromium for how to obtain the required keys and tools.