From 28f16b6fe21272c74b03e9166329733fb99f1eac Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 18 Jul 2022 23:12:09 +0000 Subject: [PATCH 01/21] Bump nokogiri from 1.13.6 to 1.13.7 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.13.6 to 1.13.7. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.13.6...v1.13.7) --- updated-dependencies: - dependency-name: nokogiri dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index 2d6d329ca..b7d7b199d 100644 --- 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.6) + nokogiri (1.13.7) mini_portile2 (~> 2.8.0) racc (~> 1.4) pathutil (0.16.2) From aff865a9e31b5bd498b483beda523c4a28e9af91 Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Tue, 19 Jul 2022 13:08:21 +0100 Subject: [PATCH 02/21] Update your_first_binary.adoc --- .../asciidoc/microcontrollers/c_sdk/your_first_binary.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/microcontrollers/c_sdk/your_first_binary.adoc b/documentation/asciidoc/microcontrollers/c_sdk/your_first_binary.adoc index 6d4009dcd..fa5164a4f 100644 --- 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[] From d258f0cd8cbb16ffd9b8918047de82bfc5cf4d61 Mon Sep 17 00:00:00 2001 From: Phil Elwell <8911409+pelwell@users.noreply.github.com> Date: Thu, 21 Jul 2022 15:06:21 +0100 Subject: [PATCH 03/21] Document the upcoming sha256 setting The next rpi-update and apt firmware packages add the sha256 setting, enabling the logging of hashes for loaded files. --- documentation/asciidoc/computers/config_txt/boot.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/documentation/asciidoc/computers/config_txt/boot.adoc b/documentation/asciidoc/computers/config_txt/boot.adoc index 1fcea1b25..f80ae1830 100644 --- 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, 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. From aeb7d3eb7b0975c6741a36b4cdebac86ded6c949 Mon Sep 17 00:00:00 2001 From: Phil Elwell <8911409+pelwell@users.noreply.github.com> Date: Thu, 21 Jul 2022 15:29:55 +0100 Subject: [PATCH 04/21] Clarify what files ares --- documentation/asciidoc/computers/config_txt/boot.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/computers/config_txt/boot.adoc b/documentation/asciidoc/computers/config_txt/boot.adoc index f80ae1830..469793326 100644 --- a/documentation/asciidoc/computers/config_txt/boot.adoc +++ b/documentation/asciidoc/computers/config_txt/boot.adoc @@ -166,7 +166,7 @@ NOTE: Unless `+${os_prefix}${overlay_prefix}README+` exists, overlays are shared [[sha256]] === `sha256` -If set to non-zero, enables the logging of SHA256 hashes for loaded files, 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. +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` From 4f93aacca3a55855516344673f05f204dde6673d Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 25 Jul 2022 23:11:40 +0000 Subject: [PATCH 05/21] Bump nokogiri from 1.13.7 to 1.13.8 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.13.7 to 1.13.8. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.13.7...v1.13.8) --- updated-dependencies: - dependency-name: nokogiri dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index b7d7b199d..f46ae2023 100644 --- 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.7) + nokogiri (1.13.8) mini_portile2 (~> 2.8.0) racc (~> 1.4) pathutil (0.16.2) From 3596739becc1ce9c2ec13fde589fe0565fe260a0 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 25 Jul 2022 23:11:49 +0000 Subject: [PATCH 06/21] Bump tzinfo from 2.0.4 to 2.0.5 Bumps [tzinfo](https://github.com/tzinfo/tzinfo) from 2.0.4 to 2.0.5. - [Release notes](https://github.com/tzinfo/tzinfo/releases) - [Changelog](https://github.com/tzinfo/tzinfo/blob/master/CHANGES.md) - [Commits](https://github.com/tzinfo/tzinfo/compare/v2.0.4...v2.0.5) --- updated-dependencies: - dependency-name: tzinfo dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] --- Gemfile.lock | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Gemfile.lock b/Gemfile.lock index b7d7b199d..4eaa4dc39 100644 --- 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) @@ -72,7 +72,7 @@ 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 (>= 1.0.0) From 16aec52fd5403464a9821cb9b82089e6cbcea926 Mon Sep 17 00:00:00 2001 From: Neil Greatorex Date: Tue, 26 Jul 2022 19:49:53 +0100 Subject: [PATCH 07/21] Update headless.adoc The headless instructions contain a small security risk. If you were to follow the instructions as written, your password would be stored in plain text in your shell history (e.g. ~/.bash_history). It's much better to get openssl to prompt you for a password - that way it's not stored anywhere. --- documentation/asciidoc/computers/configuration/headless.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/asciidoc/computers/configuration/headless.adoc b/documentation/asciidoc/computers/configuration/headless.adoc index 5c092b514..498ac08f6 100644 --- a/documentation/asciidoc/computers/configuration/headless.adoc +++ b/documentation/asciidoc/computers/configuration/headless.adoc @@ -66,9 +66,9 @@ 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. From 59ad955beba714b8adee735ac131c3cb7df658e1 Mon Sep 17 00:00:00 2001 From: Andrew Scheller Date: Thu, 28 Jul 2022 08:51:39 +0100 Subject: [PATCH 08/21] typo --- documentation/asciidoc/computers/configuration/headless.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/computers/configuration/headless.adoc b/documentation/asciidoc/computers/configuration/headless.adoc index 498ac08f6..ad7553818 100644 --- a/documentation/asciidoc/computers/configuration/headless.adoc +++ b/documentation/asciidoc/computers/configuration/headless.adoc @@ -71,4 +71,4 @@ openssl passwd -6 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. +WARNING: If you are creating this file on Microsoft Windows you should ensure that you do not 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. From b47a4fced38fe41d42b5a54cf34668e76bff25d3 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 15 Aug 2022 23:07:03 +0000 Subject: [PATCH 09/21] Bump tzinfo-data from 1.2022.1 to 1.2022.2 Bumps [tzinfo-data](https://github.com/tzinfo/tzinfo-data) from 1.2022.1 to 1.2022.2. - [Release notes](https://github.com/tzinfo/tzinfo-data/releases) - [Commits](https://github.com/tzinfo/tzinfo-data/compare/v1.2022.1...v1.2022.2) --- updated-dependencies: - dependency-name: tzinfo-data dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index 25aab1675..651335a71 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -74,7 +74,7 @@ GEM unicode-display_width (~> 1.1, >= 1.1.1) tzinfo (2.0.5) concurrent-ruby (~> 1.0) - tzinfo-data (1.2022.1) + tzinfo-data (1.2022.2) tzinfo (>= 1.0.0) unicode-display_width (1.8.0) wdm (0.1.1) From b57fab2293af8b3c6f2eb8d9da03627dad6c2c5e Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Fri, 19 Aug 2022 14:18:39 +0100 Subject: [PATCH 10/21] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 3abbe6e3d..83001be5c 100644 --- a/README.md +++ b/README.md @@ -52,6 +52,7 @@ Then you need to install Ruby, ``` $ brew install ruby@2.7 +$ gem install bundler ``` **NOTE:** Homebrew defaults to Ruby 3.0 which is incompatible with Asciidoctor. From 3119da7ec8dc83523d8216f43b48704edf594015 Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Fri, 19 Aug 2022 14:33:19 +0100 Subject: [PATCH 11/21] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 83001be5c..7935755fa 100644 --- 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. From 30ee753a659772ddddcdd13acd3c27b254326323 Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Fri, 19 Aug 2022 14:41:44 +0100 Subject: [PATCH 12/21] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7935755fa..2422f9fcf 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ Then you need to install Ruby, ``` $ brew install ruby@2.7 -$ gem install bundler +$ gem install bundler -v 2.2.15 ``` **NOTE:** Homebrew defaults to Ruby 3.0 which is incompatible with Asciidoctor. From 5dbe2cfbe5d530ee74c27531b46aacb75989a2f7 Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Fri, 19 Aug 2022 15:02:26 +0100 Subject: [PATCH 13/21] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 2422f9fcf..a76d9defc 100644 --- a/README.md +++ b/README.md @@ -97,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 From 83acc4964f922b26cfd388ec95b258fe89426994 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 22 Aug 2022 23:18:05 +0000 Subject: [PATCH 14/21] Bump tzinfo-data from 1.2022.2 to 1.2022.3 Bumps [tzinfo-data](https://github.com/tzinfo/tzinfo-data) from 1.2022.2 to 1.2022.3. - [Release notes](https://github.com/tzinfo/tzinfo-data/releases) - [Commits](https://github.com/tzinfo/tzinfo-data/compare/v1.2022.2...v1.2022.3) --- updated-dependencies: - dependency-name: tzinfo-data dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index 651335a71..957dd664d 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -74,7 +74,7 @@ GEM unicode-display_width (~> 1.1, >= 1.1.1) tzinfo (2.0.5) concurrent-ruby (~> 1.0) - tzinfo-data (1.2022.2) + tzinfo-data (1.2022.3) tzinfo (>= 1.0.0) unicode-display_width (1.8.0) wdm (0.1.1) From b66e8ce6c209119cdb62e1decf39488bbdd01883 Mon Sep 17 00:00:00 2001 From: Liz Upton Date: Tue, 23 Aug 2022 02:44:23 +0100 Subject: [PATCH 15/21] Errant full stop Aggravating full stop jumped out and hit me in the face when I was referring a blog commenter here. Ouch. --- .../asciidoc/microcontrollers/microcontroller_docs.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/microcontrollers/microcontroller_docs.adoc b/documentation/asciidoc/microcontrollers/microcontroller_docs.adoc index 6505824ae..3182fa9f8 100644 --- 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 From 746684059ddd2ce223d905de2987ed07ece881eb Mon Sep 17 00:00:00 2001 From: David Plowman Date: Fri, 2 Sep 2022 12:52:13 +0100 Subject: [PATCH 16/21] Correct the git repository where we fetch libcamera For a while now we've been building from a Raspberry Pi fork of libcamera, just so we can control extactly when it changes. The documentation should reflect this location, not the official libcamera repo. --- .../asciidoc/accessories/camera/libcamera_apps_building.adoc | 4 ++-- .../asciidoc/accessories/camera/libcamera_apps_intro.adoc | 2 +- .../asciidoc/accessories/camera/libcamera_software.adoc | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/asciidoc/accessories/camera/libcamera_apps_building.adoc b/documentation/asciidoc/accessories/camera/libcamera_apps_building.adoc index 797d7313a..0f06bb8fc 100644 --- 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 index e42c5bedf..183abe713 100644 --- 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 index 64e1edadb..dc17bb8df 100644 --- 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 From 46caf7297fb7701f0972a3a4339c5d7941c5fb0c Mon Sep 17 00:00:00 2001 From: Andrew Scheller Date: Wed, 7 Sep 2022 12:30:54 +0100 Subject: [PATCH 17/21] Revert "Warning about Windows" This reverts commit ad6558f28e46e8ac99aabe07c96668b05249f62b. --- documentation/asciidoc/computers/configuration/headless.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/documentation/asciidoc/computers/configuration/headless.adoc b/documentation/asciidoc/computers/configuration/headless.adoc index ad7553818..44a6572a5 100644 --- a/documentation/asciidoc/computers/configuration/headless.adoc +++ b/documentation/asciidoc/computers/configuration/headless.adoc @@ -71,4 +71,3 @@ openssl passwd -6 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 not 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. From 932fcb9dc25345427a12535a93cc317bb46ae8c0 Mon Sep 17 00:00:00 2001 From: Andrew Scheller Date: Thu, 8 Sep 2022 10:29:57 +0100 Subject: [PATCH 18/21] Grammar fix --- documentation/asciidoc/computers/config_txt/memory.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/computers/config_txt/memory.adoc b/documentation/asciidoc/computers/config_txt/memory.adoc index e21950afe..71d0b702a 100644 --- 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. From b2c62e08777650b64477ba1a4783633a7abb2430 Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Fri, 9 Sep 2022 15:48:42 +0100 Subject: [PATCH 19/21] Added backlog to exempt list --- .github/workflows/stale.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 9c86ebe0e..12b65ae8f 100644 --- 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 From 180b30680001c004ff925574ac64848806846e61 Mon Sep 17 00:00:00 2001 From: Carl-Daniel Hailfinger Date: Sun, 11 Sep 2022 12:08:19 +0200 Subject: [PATCH 20/21] Fix typo in vcgencmd measure_clock h264 parameter The h264 parameter was incorrectly listed as uppercase. That's not recognized by vcgencmd. --- documentation/asciidoc/computers/os/graphics-utilities.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/computers/os/graphics-utilities.adoc b/documentation/asciidoc/computers/os/graphics-utilities.adoc index 88acf0ae4..c527b313d 100644 --- 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 From 5c86e4bdf56e906bec45830993aaf665b26a8490 Mon Sep 17 00:00:00 2001 From: Alasdair Allan Date: Mon, 12 Sep 2022 09:42:37 +0100 Subject: [PATCH 21/21] Update about_pico.adoc --- .../asciidoc/microcontrollers/raspberry-pi-pico/about_pico.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/asciidoc/microcontrollers/raspberry-pi-pico/about_pico.adoc b/documentation/asciidoc/microcontrollers/raspberry-pi-pico/about_pico.adoc index 85ae3efd1..5798ba827 100644 --- 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[]