Update links from datasheets.raspberrypi.org

Now that datasheets has moved to datasheets.raspberrypi.com, update any
references to datasheets.raspberrypi.org.

documentation/asciidoc/accessories/camera/camera_hardware.adoc

@@ -231,14 +231,14 @@ The maximum exposure times of the three official Raspberry Pi cameras are given
 
 === Mechanical Drawings
 
-* Camera Module v2 https://datasheets.raspberrypi.org/camera/camera-v2-mechanical-drawing.pdf[PDF]
-* HQ Camera Module https://datasheets.raspberrypi.org/hq-camera/hq-camera-mechanical-drawing.pdf[PDF]
-* HQ Camera Module lens mount https://datasheets.raspberrypi.org/hq-camera/hq-camera-lensmount-drawing.pdf[PDF]
+* Camera Module v2 https://datasheets.raspberrypi.com/camera/camera-v2-mechanical-drawing.pdf[PDF]
+* HQ Camera Module https://datasheets.raspberrypi.com/hq-camera/hq-camera-mechanical-drawing.pdf[PDF]
+* HQ Camera Module lens mount https://datasheets.raspberrypi.com/hq-camera/hq-camera-lensmount-drawing.pdf[PDF]
 
 === Schematics
 
-* Camera Module v2 https://datasheets.raspberrypi.org/camera/camera-v2-schematics.pdf[PDF]
-* HQ Camera Module https://datasheets.raspberrypi.org/hq-camera/hq-camera-schematics.pdf[PDF]
+* Camera Module v2 https://datasheets.raspberrypi.com/camera/camera-v2-schematics.pdf[PDF]
+* HQ Camera Module https://datasheets.raspberrypi.com/hq-camera/hq-camera-schematics.pdf[PDF]
 
 === Raspberry Pi HQ Camera Filter Removal
 

documentation/asciidoc/accessories/camera/csi-2-usage.adoc

@@ -106,7 +106,7 @@ Sensors generally support https://www.kernel.org/doc/html/latest/userspace-api/m
 
 In the case of the IMX219, many of these controls map directly onto register writes to the sensor itself.
 
-Further guidance can be found in libcamera's https://git.linuxtv.org/libcamera.git/tree/Documentation/sensor_driver_requirements.rst[sensor driver requirements], and also in chapter 3 of the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Raspberry Pi Camera Tuning Guide].
+Further guidance can be found in libcamera's https://git.linuxtv.org/libcamera.git/tree/Documentation/sensor_driver_requirements.rst[sensor driver requirements], and also in chapter 3 of the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Raspberry Pi Camera Tuning Guide].
 
 ===== Device Tree
 

documentation/asciidoc/accessories/camera/libcamera_3rd_party_tuning.adoc

@@ -12,4 +12,4 @@ This _tuning file_ can be inspected and edited by users. Using the `--tuning-fil
 
 Raspberry Pi also supplies a _tuning tool_ which automates the generation of the tuning file from a few simple calibration images.
 
-Both these topics are rather beyond the scope of the documentation here, however, full information is available in the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Tuning Guide for the Raspberry Pi cameras and libcamera].
+Both these topics are rather beyond the scope of the documentation here, however, full information is available in the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Tuning Guide for the Raspberry Pi cameras and libcamera].

documentation/asciidoc/accessories/camera/libcamera_apps_intro.adoc

@@ -31,5 +31,5 @@ Raspberry Pi's implementation of `libcamera` supports not only the three standar
 
 Moreover, Raspberry Pi supplies a _tuning file_ for each of these sensors which can be edited to change the processing performed by the Pi hardware on the raw images received from the image sensor, including aspects like the colour processing, the amount of noise suppression or the behaviour of the control algorithms.
 
-For further information on `libcamera` for the Raspberry Pi, please consult the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Tuning Guide for the Raspberry Pi cameras and libcamera].
+For further information on `libcamera` for the Raspberry Pi, please consult the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Tuning Guide for the Raspberry Pi cameras and libcamera].
 

documentation/asciidoc/accessories/camera/libcamera_options_common.adoc

@@ -261,7 +261,7 @@ Sets the metering mode of the AEC/AGC algorithm. This may one of the following v
 * `average` - average or whole frame metering
 * `custom` - custom metering mode which would have to be defined in the camera tuning file.
 
-For more information on defining a custom metering mode, and also on how to adjust the region weights in the existing metering modes,please refer to the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera].
+For more information on defining a custom metering mode, and also on how to adjust the region weights in the existing metering modes,please refer to the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera].
 
 Example: `libcamera-still -o test.jpg --metering spot`
 
@@ -271,7 +271,7 @@ Example: `libcamera-still -o test.jpg --metering spot`
 
 The exposure profile may be either `normal` or `sport`. Changing the exposure profile should not affect the overall exposure of an image, but the `sport` mode will tend to prefer shorter exposure times and larger gains to achieve the same net result.
 
-Exposure profiles can be edited in the camera tuning file. Please refer to the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera] for more information.
+Exposure profiles can be edited in the camera tuning file. Please refer to the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera] for more information.
 
 Example: `libcamera-still -o test.jpg --exposure sport`
 
@@ -313,7 +313,7 @@ There is no mode that turns the AWB off, instead fixed colour gains should be sp
 
 Note that these values are only approximate, the values could vary according to the camera tuning.
 
-For more information on AWB modes and how to define a custom one, please refer to the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera].
+For more information on AWB modes and how to define a custom one, please refer to the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera].
 
 Example: `libcamera-still -o test.jpg --awb tungsten`
 
@@ -351,7 +351,7 @@ Example: `libcamera-vid -o test.h264 --denoise cdn_off`
 
 This identifies the name of the JSON format tuning file that should be used. The tuning file covers many aspects of the image processing, including the AEC/AGC, AWB, colour shading correction, colour processing, denoising and so forth.
 
-For more information on the camera tuning file, please consult the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera].
+For more information on the camera tuning file, please consult the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[Tuning guide for the Raspberry Pi cameras and libcamera].
 
 Example: `libcamera-hello --tuning-file ~/my-camera-tuning.json`
 

documentation/asciidoc/accessories/camera/libcamera_software.adoc

@@ -116,6 +116,6 @@ Also, Pi 3s do not by default use the correct GL driver, so please ensure you ha
 
 === Further Documentation
 
-You can find out more in the https://datasheets.raspberrypi.org/camera/raspberry-pi-camera-guide.pdf[_Raspberry Pi Camera Algorithm and Tuning Guide_.].
+You can find out more in the https://datasheets.raspberrypi.com/camera/raspberry-pi-camera-guide.pdf[_Raspberry Pi Camera Algorithm and Tuning Guide_.].
 
 More information on the _libcamera-apps_ is available https://github.com/raspberrypi/libcamera-apps/blob/main/README.md[on Github].

documentation/asciidoc/accessories/display/display_intro.adoc

@@ -132,7 +132,7 @@ Read our troubleshooting steps, tips, and tricks here: xref:display.adoc#trouble
 
 * Outer dimensions: 192.96 × 110.76mm
 * Viewable area: 154.08 × 85.92mm
-* https://datasheets.raspberrypi.org/display/7-inch-display-mechanical-drawing.pdf[Download mechanical drawing (PDF)]
+* https://datasheets.raspberrypi.com/display/7-inch-display-mechanical-drawing.pdf[Download mechanical drawing (PDF)]
 
 A drawing showing the radius and thickness of glass.
 

documentation/asciidoc/accessories/sense-hat.adoc

@@ -26,7 +26,7 @@ In order to work correctly, the Sense HAT requires an up-to-date kernel, I2C to
 
 == Sense HAT Hardware
 
-* Raspberry Pi https://datasheets.raspberrypi.org/sense-hat/sense-hat-schematics.pdf[Sense HAT schematics].
+* Raspberry Pi https://datasheets.raspberrypi.com/sense-hat/sense-hat-schematics.pdf[Sense HAT schematics].
 
 == Sense HAT Software
 

documentation/asciidoc/computers/compute-module/cm-peri-sw-guide.adoc

@@ -103,7 +103,7 @@ When `start.elf` runs, it first reads something called `dt-blob.bin`. This is a
 
 NOTE: the `start.elf` firmware has a xref:configuration.adoc#changing-the-default-pin-configuration['built-in' default] `dt-blob.bin` which is used if no `dt-blob.bin` is found on the root of the first FAT partition. Most Compute Module projects will want to provide their own custom `dt-blob.bin`. Note that `dt-blob.bin` specifies which pin is for HDMI hot plug detect, although this should never change on Compute Module. It can also be used to set up a GPIO as a GPCLK output, and specify an ACT LED that the GPU can use while booting. Other functions may be added in future. 
 
-https://datasheets.raspberrypi.org/cm/minimal-cm-dt-blob.dts[minimal-cm-dt-blob.dts] is an example `.dts` device tree file that sets up the HDMI hot plug detect and ACT LED and sets all other GPIOs to be inputs with default pulls.
+https://datasheets.raspberrypi.com/cm/minimal-cm-dt-blob.dts[minimal-cm-dt-blob.dts] is an example `.dts` device tree file that sets up the HDMI hot plug detect and ACT LED and sets all other GPIOs to be inputs with default pulls.
 
 To compile the `minimal-cm-dt-blob.dts` to `dt-blob.bin` use the Device Tree Compiler `dtc`:
 
@@ -174,7 +174,7 @@ Please post any issues, bugs or questions on the Raspberry Pi https://www.raspbe
 
 In this simple example we wire an NXP PCF8523 real time clock (RTC) to the CMIO board BANK1 GPIO pins: 3V3, GND, I2C1_SDA on GPIO44 and I2C1_SCL on GPIO45.
 
-Download https://datasheets.raspberrypi.org/cm/minimal-cm-dt-blob.dts[minimal-cm-dt-blob.dts] and copy it to the SD card FAT partition, located in `/boot` when the CM has booted.
+Download https://datasheets.raspberrypi.com/cm/minimal-cm-dt-blob.dts[minimal-cm-dt-blob.dts] and copy it to the SD card FAT partition, located in `/boot` when the CM has booted.
 
 Edit `minimal-cm-dt-blob.dts` and change the pin states of GPIO44 and 45 to be I2C1 with pull-ups:
 
@@ -204,7 +204,7 @@ Compile `dt-blob.bin`:
 sudo dtc -I dts -O dtb -o /boot/dt-blob.bin /boot/minimal-cm-dt-blob.dts
 ----
 
-Grab https://datasheets.raspberrypi.org/cm/example1-overlay.dts[example1-overlay.dts] and put it in `/boot` then compile it:
+Grab https://datasheets.raspberrypi.com/cm/example1-overlay.dts[example1-overlay.dts] and put it in `/boot` then compile it:
 
 ----
 sudo dtc -@ -I dts -O dtb -o /boot/overlays/example1.dtbo /boot/example1-overlay.dts

documentation/asciidoc/computers/compute-module/cmio-camera.adoc

@@ -38,7 +38,7 @@ image::images/CMIO-Cam-Adapter.jpg[Connecting the adapter board]
 +
 image::images/CMIO-Cam-GPIO.jpg[GPIO connection for a single camera]
 
-. Power the CM up and run `+sudo wget https://datasheets.raspberrypi.org/cmio/dt-blob-cam1.bin -O /boot/dt-blob.bin+`
+. Power the CM up and run `+sudo wget https://datasheets.raspberrypi.com/cmio/dt-blob-cam1.bin -O /boot/dt-blob.bin+`
 . Finally, reboot for the dt-blob.bin file to be read.
 
 To connect two cameras, follow the steps as for a single camera and then also:
@@ -47,7 +47,7 @@ To connect two cameras, follow the steps as for a single camera and then also:
 . (CM1 and CM3 only) Connect the GPIO pins for the second camera.
  image:images/CMIO-Cam-GPIO2.jpg[GPIO connection with additional camera]
 . (CM4 only) Add jumpers to J6.
-. Power up and run `+sudo wget https://datasheets.raspberrypi.org/cmio/dt-blob-dualcam.bin -O /boot/dt-blob.bin+`
+. Power up and run `+sudo wget https://datasheets.raspberrypi.com/cmio/dt-blob-dualcam.bin -O /boot/dt-blob.bin+`
 . Reboot for the dt-blob.bin file to be read.
 
 NOTE: The default wiring uses GPIOs 2&3 to control the primary camera. These GPIOs can also be used for I2C, but doing so will result in a conflict, and the camera is unlikely to work.
@@ -154,9 +154,9 @@ pin_define@CAMERA_1_SCL_PIN { type = "internal"; number = <29>; };
 [[sample-device-tree-source-files]]
 ==== Sample device tree source files
 
-https://datasheets.raspberrypi.org/cmio/dt-blob-cam1.dts[Enable CAM1 only]
+https://datasheets.raspberrypi.com/cmio/dt-blob-cam1.dts[Enable CAM1 only]
 
-https://datasheets.raspberrypi.org/cmio/dt-blob-dualcam.dts[Enable CAM1 and CAM0]
+https://datasheets.raspberrypi.com/cmio/dt-blob-dualcam.dts[Enable CAM1 and CAM0]
 
 ==== Compiling a DTS file to a device tree blob
 

documentation/asciidoc/computers/compute-module/cmio-display.adoc

@@ -22,7 +22,7 @@ Connecting to DISP1
 
 . Power up the Compute Module and run:
 +
-`+sudo wget https://datasheets.raspberrypi.org/cmio/dt-blob-disp1-only.bin -O /boot/dt-blob.bin+`
+`+sudo wget https://datasheets.raspberrypi.com/cmio/dt-blob-disp1-only.bin -O /boot/dt-blob.bin+`
 
 . Reboot for the `dt-blob.bin` file to be read.
 
@@ -39,7 +39,7 @@ Connecting to DISP0
 
 . Power up the Compute Module and run:
 +
-`+sudo wget https://datasheets.raspberrypi.org/cmio/dt-blob-disp0-only.bin -O /boot/dt-blob.bin+`
+`+sudo wget https://datasheets.raspberrypi.com/cmio/dt-blob-disp0-only.bin -O /boot/dt-blob.bin+`
 
 . Reboot for the `dt-blob.bin` file to be read.
 
@@ -63,7 +63,7 @@ image:images/CMIO-Cam-Disp-GPIO.jpg[GPIO connection for a single display and Cam
 
 . Power up the Compute Module and run:
 +
-`+sudo wget https://datasheets.raspberrypi.org/cmio/dt-blob-disp1-cam1.bin -O /boot/dt-blob.bin+`
+`+sudo wget https://datasheets.raspberrypi.com/cmio/dt-blob-disp1-cam1.bin -O /boot/dt-blob.bin+`
 
 . Reboot for the `dt-blob.bin` file to be read.
 
@@ -83,7 +83,7 @@ image:images/CMIO-Cam-Disp-GPIO.jpg[GPIO connection for a single display and Cam
 . (CM4 only) Add jumpers to J6.
 . Power up the Compute Module and run:
 +
-`+sudo wget https://datasheets.raspberrypi.org/cmio/dt-blob-disp1-cam2.bin -O /boot/dt-blob.bin+`
+`+sudo wget https://datasheets.raspberrypi.com/cmio/dt-blob-disp1-cam2.bin -O /boot/dt-blob.bin+`
 
 . Reboot for the `dt-blob.bin` file to be read.
 +
@@ -119,7 +119,7 @@ Instructions for doing this can be found on the xref:configuration.adoc#changing
 
 ==== Sources
 
-* https://datasheets.raspberrypi.org/cmio/dt-blob-disp1-only.dts[dt-blob-disp1-only.dts]
-* https://datasheets.raspberrypi.org/cmio/dt-blob-disp1-cam1.dts[dt-blob-disp1-cam1.dts]
-* https://datasheets.raspberrypi.org/cmio/dt-blob-disp1-cam2.dts[dt-blob-disp1-cam2.dts]
-* https://datasheets.raspberrypi.org/cmio/dt-blob-disp0-only.dts[dt-blob-disp0-only.dts] (Uses wiring as for CAM0)
+* https://datasheets.raspberrypi.com/cmio/dt-blob-disp1-only.dts[dt-blob-disp1-only.dts]
+* https://datasheets.raspberrypi.com/cmio/dt-blob-disp1-cam1.dts[dt-blob-disp1-cam1.dts]
+* https://datasheets.raspberrypi.com/cmio/dt-blob-disp1-cam2.dts[dt-blob-disp1-cam2.dts]
+* https://datasheets.raspberrypi.com/cmio/dt-blob-disp0-only.dts[dt-blob-disp0-only.dts] (Uses wiring as for CAM0)

documentation/asciidoc/computers/compute-module/datasheet.adoc

@@ -4,41 +4,41 @@
 
 The latest version of the Compute Module is the Compute Module 4 (CM4). It is the recommended Compute Module for all current and future development.
 
-* https://datasheets.raspberrypi.org/cm4/cm4-datasheet.pdf[Compute Module 4 Datasheet]
-* https://datasheets.raspberrypi.org/cm4io/cm4io-datasheet.pdf[Compute Module 4 IO Board Datasheet]
+* https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf[Compute Module 4 Datasheet]
+* https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf[Compute Module 4 IO Board Datasheet]
 
 NOTE: Schematics are not available for the Compute Module 4, but are available for the IO board.
 
 Schematics for the CMIO4 board are included in the datasheet,
 
-* https://datasheets.raspberrypi.org/cm4io/cm4io-datasheet.pdf[Compute Module 4 IO Board Datasheet] (including schematics)
+* https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf[Compute Module 4 IO Board Datasheet] (including schematics)
 
 There is also a KiCAD PCB design set available:
 
-* https://datasheets.raspberrypi.org/cm4io/CM4IO-KiCAD.zip[Compute Module 4 IO Board KiCAD files]
+* https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip[Compute Module 4 IO Board KiCAD files]
 
 === Older Products
 
 Raspberry Pi CM1, CM3 and CM3L are supported products with an End-of-Life (EOL) date no earlier than January 2026. For customers embarking on new designs, Raspberry Pi recommends using the newer Compute Module 3+, which offers improved thermal performance, and a wider range of Flash memory options.
 
-* https://datasheets.raspberrypi.org/cm/cm1-and-cm3-datasheet.pdf[Compute Module and Compute Module 3]
+* https://datasheets.raspberrypi.com/cm/cm1-and-cm3-datasheet.pdf[Compute Module and Compute Module 3]
 
 Raspberry Pi CM3+ and CM3+ Lite are supported prodicts with an End-of-Life (EOL) date no earlier than January 2026.
 
-* https://datasheets.raspberrypi.org/cm/cm3-plus-datasheet.pdf[Compute Module 3+]
+* https://datasheets.raspberrypi.com/cm/cm3-plus-datasheet.pdf[Compute Module 3+]
 
 Schematics for the Compute Module 1, 3 and 3L
 
-* https://datasheets.raspberrypi.org/cm/cm1-schematics.pdf[CM Rev 1.1]
-* https://datasheets.raspberrypi.org/cm/cm3-schematics.pdf[CM3 and CM3L Rev 1.0]
+* https://datasheets.raspberrypi.com/cm/cm1-schematics.pdf[CM Rev 1.1]
+* https://datasheets.raspberrypi.com/cm/cm3-schematics.pdf[CM3 and CM3L Rev 1.0]
 
 Schematics for the Compute Module IO board (CMIO):
 
-* https://datasheets.raspberrypi.org/cmio/cmio-schematics.pdf[CMIO Rev 3.0] (Supports CM1, CM3, CM3L, CM3+ and CM3+L)
+* https://datasheets.raspberrypi.com/cmio/cmio-schematics.pdf[CMIO Rev 3.0] (Supports CM1, CM3, CM3L, CM3+ and CM3+L)
 
 Schematics for the Compute Module camera/display adapter board (CMCDA):
 
-* https://datasheets.raspberrypi.org/cmcda/cmcda-schematics.pdf[CMCDA Rev 1.1]
+* https://datasheets.raspberrypi.com/cmcda/cmcda-schematics.pdf[CMCDA Rev 1.1]
 
 ==== Under Voltage Detection
 

documentation/asciidoc/computers/compute-module/designfiles.adoc

@@ -5,18 +5,18 @@
 
 Design data for the Compute Module 4 IO board can be found in its datasheet:
 
-* https://datasheets.raspberrypi.org/cm4io/cm4io-datasheet.pdf[Compute Module 4 IO Board datasheet]
+* https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf[Compute Module 4 IO Board datasheet]
 
 There is also a KiCAD PCB design set available:
 
-* https://datasheets.raspberrypi.org/cm4io/CM4IO-KiCAD.zip[Compute Module 4 IO Board KiCAD files]
+* https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip[Compute Module 4 IO Board KiCAD files]
 
 [discrete]
 === Older Products
 
-* https://datasheets.raspberrypi.org/cmio/RPi-CMIO-R1P2.zip[CMIO Rev 1.2]
-* https://datasheets.raspberrypi.org/cmio/RPi-CMIO-R3P0.zip[CMIO Rev 3.0]
+* https://datasheets.raspberrypi.com/cmio/RPi-CMIO-R1P2.zip[CMIO Rev 1.2]
+* https://datasheets.raspberrypi.com/cmio/RPi-CMIO-R3P0.zip[CMIO Rev 3.0]
 
 Design data for the Compute Module camera/display adapter board (CMCDA):
 
-* https://datasheets.raspberrypi.org/cmcda/RPi-CMCDA-1P1.zip[CMCDA Rev 1.1]
+* https://datasheets.raspberrypi.com/cmcda/RPi-CMCDA-1P1.zip[CMCDA Rev 1.1]

documentation/asciidoc/computers/configuration/pin-configuration.adoc

@@ -8,7 +8,7 @@ As of July 2014, the Raspberry Pi firmware supports custom default pin configura
 
 During the bootup sequence, the GPIO pins go through various actions.
 
-. Power-on -- pins default to inputs with default pulls; the default pulls for each pin are described in the https://datasheets.raspberrypi.org/bcm2835/bcm2835-peripherals.pdf[datasheet]
+. Power-on -- pins default to inputs with default pulls; the default pulls for each pin are described in the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[datasheet]
 . Setting by the bootrom
 . Setting by `bootcode.bin`
 . Setting by `dt-blob.bin` (this page)

documentation/asciidoc/computers/configuration/uart.adoc

@@ -222,4 +222,4 @@ The particular deficiencies of the mini UART compared to a PL011 are :
 * No receive timeout interrupt
 * No DCD, DSR, DTR or RI signals
 
-Further documentation on the mini UART can be found in the https://datasheets.raspberrypi.org/bcm2835/bcm2835-peripherals.pdf[SoC peripherals document].
+Further documentation on the mini UART can be found in the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[SoC peripherals document].