Merge branch 'master' into debian/buster

firmware/raspberry_pi4_network_boot_beta.md

@@ -40,9 +40,11 @@ sudo echo FIRMWARE_RELEASE_STATUS="beta" > /etc/default/rpi-eeprom-update
 
 ### Configuration - Enable network boot
 Network boot is not enabled by default in the bootloader. To enable it the bootloader configuration file must be edited.
+
+**NOTE:** The `/lib/firmware...` file listed in the code block below should not be copied directly, as it requires a date be maually used. There are several versions of the beta bootloader inside that directory, so make sure to select the most up-to-date version for your Raspberry Pi.
 ```
 # Extract the configuration file
-cp /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2019-09-23.bin pieeprom.bin
+cp /lib/firmware/raspberrypi/bootloader/beta/pieeprom-YYYY-MM-DD.bin pieeprom.bin
 rpi-eeprom-config pieeprom.bin > bootconf.txt
 
 # Enable network boot

firmware/release-notes.md

@@ -1,5 +1,16 @@
 # Raspberry Pi4 bootloader EEPROM release notes
 
+## 2020-02-27 rpi-eeprom-update & firmware
+    * Remove the dependency check for the vl805 utility. This is deprecated
+      and there is no 64-bit version. The file is still available in Github
+      for anyone who wants to continue using USE_FLASHROM or create their
+      own scripts.
+    * Add a stable firmware directory based on the latest beta release.
+      Stable should be interpreted as feature-freeze releases. In this
+      case the core network boot is stable enough for most scenarios
+      and this de-risks adding new more experimental features in the
+      beta folder.
+
 ## 2020-01-22 - vl805 00137ad
     * Set the default/critical vl805 version to be 00137ad. This has the 
       same power savings as 0137ab but with fixes for USB webcams.

rpi-eeprom-update

@@ -11,8 +11,7 @@ if [ -f /etc/default/rpi-eeprom-update ]; then
 fi
 
 FIRMWARE_ROOT=${FIRMWARE_ROOT:-/lib/firmware/raspberrypi/bootloader}
-# May be used to select beta releases instead of the default critical
+# May be used to select beta or stable releases instead of the default critical updates.
-# updates.
 FIRMWARE_RELEASE_STATUS=${FIRMWARE_RELEASE_STATUS:-critical}
 FIRMWARE_IMAGE_DIR=${FIRMWARE_IMAGE_DIR:-${FIRMWARE_ROOT}/${FIRMWARE_RELEASE_STATUS}}
 FIRMWARE_BACKUP_DIR=${FIRMWARE_BACKUP_DIR:-/var/lib/raspberrypi/bootloader/backup}
@@ -262,10 +261,6 @@ checkDependencies() {
       FIRMWARE_IMAGE_DIR="${FIRMWARE_IMAGE_DIR}-${BOARD_REVISION}"
    fi
 
-   if ! command -v vl805 > /dev/null; then
-      die "vl805 command not found. On Debian, try reinstalling the rpi-eeprom package."
-   fi
-
    if vcgencmd bootloader_config | grep -qi "Command not registered"; then
       die "vcgencmd: 'bootloader_config' command not supported. Please update VC firmware and reboot."
    fi
@@ -362,10 +357,10 @@ those devices to stop working until after the system is reboot.
 FIRMWARE_RELEASE_STATUS
 
 Specifies the release status of the firmware to apply. The default is 'critical'
-which is the most stable production version. Alternatively, 'beta' may be selected
+which is the most stable production version. Alternatively, 'stable' or
-for development releases.
+'beta' may be selected for development releases.
 A 'critical' update is the latest stable production version and is normally
-only updated after it has been tested via the 'beta' release.
+only updated after it has been tested via the 'beta' and then a 'stable' release.
 Before selecting a firmware release directory this script checks whether there
 is a board revision specific variant e.g. critical-c03111. If present then the
 board-revision specific version is used in preference.