firmware: Promote the latest beta firmware to stable

The beta release with supports network boot is now stable enough
for most configurations. This is now frozen except for major bugs
in order to allow more experimental features to be released as
beta.
This commit is contained in:
Tim Gover
2020-02-27 14:47:21 +00:00
parent cd0eaf3c68
commit 3be67ad8a8
5 changed files with 15 additions and 5 deletions

View File

@@ -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.

Binary file not shown.

Binary file not shown.

Binary file not shown.

View File

@@ -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
# updates.
# May be used to select beta or stable releases instead of the default critical 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}
@@ -358,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
for development releases.
which is the most stable production version. Alternatively, 'stable' or
'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.