This bootloader firmware is deprecated and should no longer be
included in the rpi-eeprom package. It's still available in the
Git history if anyone *really* wants this.
Select the recovery.bin to use according to FIRMWARE_RELEASE_STATUS
in order to allow a beta test version of recovery.bin to be provided
without risking breaking the stable version of recovery.bin
Update the rpi-eeprom-config tool to accept config files of up to
2024 byte. The config section has a 24byte header so the section is
always <= 2KiB.
This allows a reasonably large user-data section in the config file
accessible via 'vcgencmd bootloader_config' as an alternative to
customer OTP data.
N.B. The vcgencmd uses a single VCHIQ message which is limited to
4092 bytes. Setting a 2KiB limit here gives room for user-data plus
some spare space for future config expansion before an VCHIQ bulk
message or an extra EEPROM 4KiB page is required.
The concept of a safe mode recovery.bin bootloader was dropped in favour
of a recovery.bin which renames itself after updating the EEPROM. Remove
the old comments.
If the size of bootconf.txt is reduced then set the unused data
to all ones instead of leaving garbage at the end. The EEPROM
header contains the actual file but this makes it easier to
verify the image and makes overreads more obvious.
Fix a bug which could cause the rename of recovery.bin to fail if
RECOVERY.000 (or higher number) existed and was the last root
directory entry in a FAT16 partition. This is unlikely be a problem
for most updates because the rpi-eeprom-update package removes the
renamed recovery.bin files when it runs.
Function does not necessarily check for latest version. Also, it does not actually get the update, just the version, so rename function to 'getUpdateVersion' to match 'getCurrentVersion'. Similarly with 2 variable names.
* Use vcgencmd otp_dump to get the board-revision because the format
is predictable.
* Change the -f completion message to indicate that the update is
scheduled rather than complete.
* Add some notes to help about the update mechanism.
