raspberrypi · aallan · May 7, 2022 · Apr 11, 2022 · Apr 11, 2022 · Apr 12, 2022
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -5,3 +5,8 @@ updates:
     schedule:
       interval: "weekly"
     target-branch: "develop"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule: 
+      interval: weekly
+    target-branch: develop
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -55,7 +55,7 @@ GEM
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    nokogiri (1.13.3)
+    nokogiri (1.13.4)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
     pathutil (0.16.2)

diff --git a/documentation/asciidoc/accessories/camera.adoc b/documentation/asciidoc/accessories/camera.adoc
@@ -56,6 +56,8 @@ include::camera/timelapse.adoc[]
 
 include::camera/gstreamer.adoc[]
 
+include::camera/qt.adoc[]
+
 include::camera/v4l2.adoc[]
 
 include::camera/csi-2-usage.adoc[]

diff --git a/documentation/asciidoc/accessories/camera/camera_hardware.adoc b/documentation/asciidoc/accessories/camera/camera_hardware.adoc
@@ -225,7 +225,7 @@ The maximum exposure times of the three official Raspberry Pi cameras are given
 | V2 (IMX219)
 | 10
 
-| HQ (IMX417)
+| HQ (IMX477)
 | 230
 |===
 

diff --git a/documentation/asciidoc/accessories/camera/qt.adoc b/documentation/asciidoc/accessories/camera/qt.adoc
@@ -0,0 +1,22 @@
+=== Using _libcamera_ and _Qt_ together
+
+_Qt_ is a popular application framework and GUI toolkit, and indeed _libcamera-apps_ optionally makes use of it to implement a camera preview window.
+
+However, _Qt_ defines certain symbols as macros in the global namespace (such as `slot` and `emit`) and this causes errors when including _libcamera_ files. The problem is common to all platforms trying to use both _Qt_ and _libcamera_ and not specific to Raspberry Pi. Nonetheless we suggest that developers experiencing difficulties try the following workarounds.
+
+1. _libcamera_ include files, or files that include _libcamera_ files (such as _libcamera-apps_ files), should be listed before any _Qt_ header files where possible.
+
+2. If you do need to mix your Qt application files with libcamera includes, replace `signals:` with `Q_SIGNALS:`, `slots:` with `Q_SLOTS:`, `emit` with `Q_EMIT` and `foreach` with `Q_FOREACH`.
+
+3. Before any _libcamera_ include files, add
++
+----
+#undef signals
+#undef slots
+#undef emit
+#undef foreach
+----
+
+4. If you are using _qmake_, add `CONFIG += no_keywords` to the project file. If using _cmake_, add `SET(QT_NO_KEYWORDS ON)`.
+
+We are not aware of any plans for the underlying library problems to be addressed.
diff --git a/documentation/asciidoc/computers/configuration/headless.adoc b/documentation/asciidoc/computers/configuration/headless.adoc
@@ -4,7 +4,7 @@ If you do not use a monitor or keyboard to run your Raspberry Pi (known as headl
 
 Once an image is created on an SD card, by inserting it into a card reader on a Linux or Windows machines the xref:configuration.adoc#the-boot-folder[boot folder] can be accessed. Adding certain files to this folder will activate certain setup features on the first boot of the Raspberry Pi.
 
-IMPORTANT: If you are installing Raspberry Pi OS Lite and intend to run it headless, you will need to create a new user account. Since you will not be able to create the user account on first boot, you *MUST* add a `userconf.txt` file to the boot folder to create a user on first boot.
+IMPORTANT: If you are installing Raspberry Pi OS, and intend to run it headless, you will need to create a new user account. Since you will not be able to create the user account xref:getting-started.adoc#configuration-on-first-boot[using the first-boot wizard] as it requires both a monitor and a keyboard, you *MUST* add a `userconf.txt` file to the boot folder to create a user on first boot or configure the OS with a user account using the xref:getting-started.adoc#advanced-options[Advanced Menu] in the Rapsberry Pi Imager.
 
 === Configuring Networking
 

diff --git a/documentation/asciidoc/computers/configuration/led_blink_warnings.adoc b/documentation/asciidoc/computers/configuration/led_blink_warnings.adoc
@@ -58,6 +58,10 @@ If a Raspberry Pi fails to boot for some reason, or has to shut down, in many ca
 | 3
 | I2C error - Pi 4
 
+| 3
+| 4
+| Secure-boot configuration is not valid
+
 | 4
 | 4
 | Unsupported board type

diff --git a/documentation/asciidoc/computers/linux_kernel/building.adoc b/documentation/asciidoc/computers/linux_kernel/building.adoc
@@ -118,12 +118,12 @@ For the 64-bit kernel:
 
 [,bash]
 ----
-make -j4 Image modules dtbs
+make -j4 Image.gz modules dtbs
 sudo make modules_install
 sudo cp arch/arm64/boot/dts/broadcom/*.dtb /boot/
 sudo cp arch/arm64/boot/dts/overlays/*.dtb* /boot/overlays/
 sudo cp arch/arm64/boot/dts/overlays/README /boot/overlays/
-sudo cp arch/arm64/boot/Image /boot/$KERNEL.img
+sudo cp arch/arm64/boot/Image.gz /boot/$KERNEL.img
 ----
 
 NOTE: On a Raspberry Pi 2/3/4, the `-j4` flag splits the work between all four cores, speeding up compilation significantly.

diff --git a/documentation/asciidoc/computers/processors/bcm2835.adoc b/documentation/asciidoc/computers/processors/bcm2835.adoc
@@ -1,12 +1,11 @@
 == BCM2835
 
-The BCM2835 is the Broadcom chip used in the Raspberry Pi 1 Models A, A+, B, B+, the Raspberry Pi Zero, the Raspberry Pi Zero W, and the Raspberry Pi Compute Module 1. Some details of the chip can be found in the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[Peripheral specification] document.
+The BCM2835 is the Broadcom chip used in the Raspberry Pi 1 Models A, A+, B, B+, the Raspberry Pi Zero, the Raspberry Pi Zero W, and the Raspberry Pi Compute Module 1. Some details of the chip can be found in the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[Peripheral specification] document. It contains a single core ARM1176JZF-S processor.
 
 NOTE: This document contains a number of errors. However there is a list of currently known https://elinux.org/BCM2835_datasheet_errata[errata].
 
 Other information regarding the processor can be found in the following documents;
 
 * https://docs.broadcom.com/docs/12358545[GPU documentation] and https://docs.broadcom.com/docs/12358546[open-source driver]
-* https://www.arm.com/products/processors/classic/arm11/arm1176.php[ARM1176 processor]
-* http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0301h/index.html[ARM1176JZF-S]
+* https://developer.arm.com/documentation/ddi0301[ARM1176JZF-S]
 
diff --git a/documentation/asciidoc/computers/raspberry-pi/revision-codes.adoc b/documentation/asciidoc/computers/raspberry-pi/revision-codes.adoc
@@ -504,6 +504,12 @@ NOTE: This list is not exhaustive - there may be codes in use that are not in th
 | 2GB
 | Sony UK
 
+| b03115
+| 4B
+| 1.5
+| 2GB
+| Sony UK
+
 | c03111
 | 4B
 | 1.1
@@ -522,12 +528,24 @@ NOTE: This list is not exhaustive - there may be codes in use that are not in th
 | 4GB
 | Sony UK
 
+| c03115
+| 4B
+| 1.5
+| 4GB
+| Sony UK
+
 | d03114
 | 4B
 | 1.4
 | 8GB
 | Sony UK
 
+| d03115
+| 4B
+| 1.5
+| 8GB
+| Sony UK
+
 | c03130
 | Pi 400
 | 1.0

diff --git a/documentation/asciidoc/computers/using_linux/linux-bash.adoc b/documentation/asciidoc/computers/using_linux/linux-bash.adoc
@@ -1,4 +1,4 @@
-== The `.bashrc ` File
+== The `.bashrc` File
 
 In your home folder you will find a hidden file called `.bashrc` which contains some user configuration options. You can edit this file to suit your needs. Changes made in this file will be actioned the next time a terminal is opened, since that is when the `.bashrc` file is read.
 

diff --git a/jekyll-assets/_includes/footer.html b/jekyll-assets/_includes/footer.html
@@ -161,6 +161,7 @@
           <li class="__rptl-footer-item"><a href="/for-industry/thin-clients/" class="__rptl-footer-link">Thin clients</a></li>
           <li class="__rptl-footer-item"><a href="/for-industry/integrator-programme/" class="__rptl-footer-link">Powered by Raspberry Pi</a></li>
           <li class="__rptl-footer-item"><a href="/for-industry/design-partners/" class="__rptl-footer-link">Design partners</a></li>
+          <li class="__rptl-footer-item"><a href="/success-stories/" class="__rptl-footer-link">Success stories</a></li>
         </ul>
         <div class="__rptl-footer-heading">Hardware</div>
         <ul class="__rptl-footer-list">
-Original file line number
+Diff line change
@@ Expand Up @@
     | V2 (IMX219)
     | 10
-    | HQ (IMX417)
+    | HQ (IMX477)
     | 230
     |===
@@ Expand Down @@