raspberrypi/rpi-eeprom
1
0
Fork 0
mirror of https://github.com/raspberrypi/rpi-eeprom.git synced 2026-01-20 21:13:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

rpi-eeprom-update: Update help for FIRMWARE_RELEASE_STATUS

Browse Source
This commit is contained in:
Tim Gover
2020-05-26 15:01:28 +01:00
parent 5fb23cfcb8
commit 7c181f40f2
1 changed files with 17 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
rpi-eeprom-update
View File

@@ -374,15 +374,27 @@ 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, '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' and then a 'stable' release.
Specifies the release status of the firmware to apply. The default is 'critical'.
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.
Release status:
critical: The latest production release plus important security or hardware compatibility bug fixes.
stable: Contains new features have already undergone some beta testing.
These are candidats for new production releases.
beta: New features, bug fixes for development/test purposes. Use at your own
risk!
As far as rpi-eeprom-update is concerned FIRMWARE_RELEASE_STATUS is just
the subdirectory mapping under ${FIRMWARE_ROOT}. Therefore, custom release
directories are supported by creating the relevant directory and changing
the FIRMWARE_RELEASE_STATUS environment variable.
Examples:
To extract the configuration file from an EEPROM image:
rpi-eeprom-config pieeprom.bin --out bootconf.txt