raspberrypi · aallan · Sep 12, 2022 · Jul 18, 2022 · Jul 19, 2022 · Jul 21, 2022
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
@@ -20,7 +20,7 @@ jobs:
         stale-pr-message: 'This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.'
         stale-issue-label: 'stale issue'
         stale-pr-label: 'stale pull request'
-        exempt-issue-labels: 'ready to merge,ready for copy-edit,paused,in progress,linked pull request'
-        exempt-pr-labels: 'ready to merge,ready for copy-edit,paused,in progress'
+        exempt-issue-labels: 'ready to merge,ready for copy-edit,paused,in progress,linked pull request,backlog'
+        exempt-pr-labels: 'ready to merge,ready for copy-edit,paused,in progress,backlog'
         days-before-stale: 60
         days-before-close: 7
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -5,7 +5,7 @@ GEM
       public_suffix (>= 2.0.2, < 5.0)
     asciidoctor (2.0.15)
     colorator (1.1.0)
-    concurrent-ruby (1.1.9)
+    concurrent-ruby (1.1.10)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
@@ -55,7 +55,7 @@ GEM
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    nokogiri (1.13.6)
+    nokogiri (1.13.8)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
     pathutil (0.16.2)
@@ -72,9 +72,9 @@ GEM
       ffi (~> 1.9)
     terminal-table (2.0.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
-    tzinfo (2.0.4)
+    tzinfo (2.0.5)
       concurrent-ruby (~> 1.0)
-    tzinfo-data (1.2022.1)
+    tzinfo-data (1.2022.3)
       tzinfo (>= 1.0.0)
     unicode-display_width (1.8.0)
     wdm (0.1.1)

diff --git a/README.md b/README.md
@@ -36,7 +36,7 @@ export PATH="$PATH:$GEM_HOME/bin"
 
 and close and relaunch your Terminal window to have these new variables activated. Finally, run
 ```
-$ gem install bundler
+$ gem install bundler -v 2.2.15
 ```
 to install the latest version of the Ruby `bundle` command.
 
@@ -52,6 +52,7 @@ Then you need to install Ruby,
 
 ```
 $ brew install ruby@2.7
+$ gem install bundler -v 2.2.15
 ```
 
 **NOTE:** Homebrew defaults to Ruby 3.0 which is incompatible with Asciidoctor.
@@ -96,6 +97,7 @@ Go ahead and `brew install` the other dependencies,
 $ brew install python@3
 $ brew install ninja
 $ brew install gumbo-parser
+$ pip3 install pyyaml
 ```
 
 ### Install Scripting Dependencies

diff --git a/documentation/asciidoc/accessories/camera/libcamera_apps_building.adoc b/documentation/asciidoc/accessories/camera/libcamera_apps_building.adoc
@@ -64,11 +64,11 @@ In the `meson` commands below we have enabled the _gstreamer_ plugin. If you _do
 sudo apt install -y libglib2.0-dev libgstreamer-plugins-base1.0-dev
 ----
 
-Now we can check out and build `libcamera` itself.
+Now we can check out and build `libcamera` itself. We check out Raspberry Pi's fork of libcamera which tracks the official repository but lets us control exactly when we pick up new features.
 
 ----
 cd
-git clone git://linuxtv.org/libcamera.git
+git clone https://github.com/raspberrypi/libcamera.git
 cd libcamera
 ----
 

diff --git a/documentation/asciidoc/accessories/camera/libcamera_apps_intro.adoc b/documentation/asciidoc/accessories/camera/libcamera_apps_intro.adoc
@@ -21,7 +21,7 @@ Raspberry Pi's `libcamera-apps` are not only command line applications that make
 
 `libcamera` is an open source Linux community project. More information is available at the https://libcamera.org[`libcamera` website].
 
-The `libcamera` source code can be found and checked out from the https://git.linuxtv.org/libcamera.git/[official libcamera repository].
+The `libcamera` source code can be found and checked out from the https://git.linuxtv.org/libcamera.git/[official libcamera repository], although we work from a https://github.com/raspberrypi/libcamera.git[fork] that lets us control when we get _libcamera_ updates.
 
 Underneath the `libcamera` core, Raspberry Pi provides a custom _pipeline handler_, which is the layer that `libcamera` uses to drive the sensor and ISP (Image Signal Processor) on the Raspberry Pi itself. Also part of this is a collection of well-known _control algorithms_, or _IPAs_ (Image Processing Algorithms) in `libcamera` parlance, such as AEC/AGC (Auto Exposure/Gain Control), AWB (Auto White Balance), ALSC (Auto Lens Shading Correction) and so on.
 

diff --git a/documentation/asciidoc/accessories/camera/libcamera_software.adoc b/documentation/asciidoc/accessories/camera/libcamera_software.adoc
@@ -62,7 +62,7 @@ We can now check out the code and build _libcamera_ as follows. Note that if you
 
 [,bash]
 ----
-git clone git://linuxtv.org/libcamera.git
+git clone https://github.com/raspberrypi/libcamera.git
 cd libcamera
 meson build
 cd build

diff --git a/documentation/asciidoc/computers/config_txt/boot.adoc b/documentation/asciidoc/computers/config_txt/boot.adoc
@@ -163,6 +163,11 @@ Specifies a subdirectory/prefix from which to load overlays - defaults to `overl
 
 NOTE: Unless `+${os_prefix}${overlay_prefix}README+` exists, overlays are shared with the main OS (i.e. `os_prefix` is ignored).
 
+[[sha256]]
+=== `sha256`
+
+If set to non-zero, enables the logging of SHA256 hashes for loaded files (the kernel, initramfs, Device Tree .dtb file and overlays), as generated by the `sha256sum` utility. The logging output goes to the UART if enabled, and is also accessible via `sudo vcdbg log msg`. This option may be useful when debugging booting problems, but at the cost of potentially adding _many_ seconds to the boot time. Defaults to 0 on all platforms.
+
 === `uart_2ndstage`
 
 Setting `uart_2ndstage=1` causes the second-stage loader (`bootcode.bin` on devices prior to the Raspberry Pi 4, or the boot code in the  EEPROM for Raspberry Pi 4 devices) and the main firmware (`start*.elf`) to output diagnostic information to UART0.

diff --git a/documentation/asciidoc/computers/config_txt/memory.adoc b/documentation/asciidoc/computers/config_txt/memory.adoc
@@ -55,4 +55,4 @@ This value will be clamped between a minimum of 128MB, and a maximum of the tota
 
 === `disable_l2cache`
 
-Setting this to `1` disables the CPUs access to the GPUs L2 cache and requires a corresponding L2 disabled kernel. Default value on BCM2835 is `0`. On BCM2836, BCM2837, and BCM2711, the ARMs have their own L2 cache and therefore the default is `1`. The standard Raspberry Pi `kernel.img` and `kernel7.img` builds reflect this difference in cache setting.
+Setting this to `1` disables the CPU's access to the GPU's L2 cache and requires a corresponding L2 disabled kernel. Default value on BCM2835 is `0`. On BCM2836, BCM2837, and BCM2711, the ARMs have their own L2 cache and therefore the default is `1`. The standard Raspberry Pi `kernel.img` and `kernel7.img` builds reflect this difference in cache setting.
diff --git a/documentation/asciidoc/computers/configuration/headless.adoc b/documentation/asciidoc/computers/configuration/headless.adoc
@@ -66,9 +66,8 @@ This file should contain a single line of text, consisting of `username:password
 To generate the encrypted password, the easiest way is to use OpenSSL on a Raspberry Pi that is already running – open a terminal window and enter:
 
 ----
-echo 'mypassword' | openssl passwd -6 -stdin
+openssl passwd -6
 ----
 
-This will produce what looks like a string of random characters, which is actually an encrypted version of the supplied password.
+This will prompt you to enter your password, and verify it. It will then produce what looks like a string of random characters, which is actually an encrypted version of the supplied password.
 
-WARNING: If you are creating this file on Microsoft Windows you should ensure that you do no add a newline to the end of the file. In Windows, lines end with both the line feed and carriage return ASCII characters, but Unix uses only a line feed and treats the additional carriage return character as part of the password hash.
diff --git a/documentation/asciidoc/computers/os/graphics-utilities.adoc b/documentation/asciidoc/computers/os/graphics-utilities.adoc
@@ -155,7 +155,7 @@ This returns the current frequency of the specified clock. The options are:
 | core
 | GPU core
 
-| H264
+| h264
 | H.264 block
 
 | isp

diff --git a/documentation/asciidoc/microcontrollers/c_sdk/your_first_binary.adoc b/documentation/asciidoc/microcontrollers/c_sdk/your_first_binary.adoc
@@ -2,7 +2,7 @@
 
 === Blink an LED
 
-The first program anyone writes when using a new microcontroller is to blink an LED on and off. The Raspberry Pi Pico comes with a single LED on-board. The LED is connected to `GP25` on the board's Raspberry RP2040 for Pico, and `WL_GPIO0` on the Infineon 43439 wireless chip for Pico W.
+The first program anyone writes when using a new microcontroller is to blink an LED on and off. The Raspberry Pi Pico comes with a single LED on-board. The LED is connected to `GP25` on the board's Raspberry Pi RP2040 for Pico, and `WL_GPIO0` on the Infineon 43439 wireless chip for Pico W.
 
 image:images/Blink-an-LED-640x360-v2.gif[]
 

diff --git a/documentation/asciidoc/microcontrollers/microcontroller_docs.adoc b/documentation/asciidoc/microcontrollers/microcontroller_docs.adoc
@@ -12,7 +12,7 @@ https://datasheets.raspberrypi.com/rp2040/hardware-design-with-rp2040.pdf[Hardwa
 
 === Raspberry Pi Pico
 
-https://datasheets.raspberrypi.com/pico/pico-datasheet.pdf[Raspberry Pi Pico Datasheet]:: An RP2040-based microcontroller board.
+https://datasheets.raspberrypi.com/pico/pico-datasheet.pdf[Raspberry Pi Pico Datasheet]:: An RP2040-based microcontroller board
 
 https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf[Getting started with Raspberry Pi Pico]:: C/{cpp} development with Raspberry Pi Pico and other RP2040-based microcontroller boards
 

diff --git a/documentation/asciidoc/microcontrollers/raspberry-pi-pico/about_pico.adoc b/documentation/asciidoc/microcontrollers/raspberry-pi-pico/about_pico.adoc
@@ -58,6 +58,8 @@ For best wireless performance, the antenna should be in free space. For instance
 antenna can reduce its performance both in terms of gain and bandwidth. Adding grounded metal to the sides of the
 antenna can improve the antenna’s bandwidth.
 
+NOTE: The CYW43439 wireless chip is connected via SPI to the RP2040. While the CYW43439 supports both 802.11 wireless and Bluetooth, initially Pico W does not have Bluetooth support. Support may be added later, and will use the same SPI interface. If support is added existing hardware may require a firmware update to support Bluetooth, but there will be no hardware modifications needed.
+
 === Pinout and design files
 
 image::images/picow-pinout.svg[]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -55,4 +55,4 @@ This value will be clamped between a minimum of 128MB, and a maximum of the tota

		=== `disable_l2cache`

		Setting this to `1` disables the CPUs access to the GPUs L2 cache and requires a corresponding L2 disabled kernel. Default value on BCM2835 is `0`. On BCM2836, BCM2837, and BCM2711, the ARMs have their own L2 cache and therefore the default is `1`. The standard Raspberry Pi `kernel.img` and `kernel7.img` builds reflect this difference in cache setting.
		Setting this to `1` disables the CPU's access to the GPU's L2 cache and requires a corresponding L2 disabled kernel. Default value on BCM2835 is `0`. On BCM2836, BCM2837, and BCM2711, the ARMs have their own L2 cache and therefore the default is `1`. The standard Raspberry Pi `kernel.img` and `kernel7.img` builds reflect this difference in cache setting.
-Original file line number
+Diff line change
@@ Expand Up @@
     | core
     | GPU core
-    | H264
+    | h264
     | H.264 block
     | isp
@@ Expand Down @@