diff options
| author | Stijn Tintel <stijn@linux-ipv6.be> | 2017-10-21 14:51:14 +0300 |
|---|---|---|
| committer | Stijn Tintel <stijn@linux-ipv6.be> | 2017-10-23 12:50:30 +0300 |
| commit | a48e5bea12911da1647a499a7b74c2408a04ac90 (patch) | |
| tree | 4a23e582f7ea41dd99002c3278e20f7fbcf439b2 /rules.mk | |
| parent | f7a6fd31539be54d14d7c52b491b40b26bf8f740 (diff) | |
| download | upstream-a48e5bea12911da1647a499a7b74c2408a04ac90.tar.gz upstream-a48e5bea12911da1647a499a7b74c2408a04ac90.tar.bz2 upstream-a48e5bea12911da1647a499a7b74c2408a04ac90.zip | |
brcm2708: restore /boot/config.txt before reboot
The Raspberry Pi bootloader reads configuration values from config.txt
in the boot partition. This file allows to specify the amount of memory
to assign to the GPU, the license keys for hardware MPEG-2 and VC-1
decoding, Device Tree parameters and overlays, and lots of other things.
Since sysupgrade only restores the configuration after booting the newly
flashed image, these values will not be active, even if sysupgrade would
save /boot/config.txt. To solve this, add the file to the files to be
backed up, and restore it in platform_copy_config, before reboot.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Diffstat (limited to 'rules.mk')
0 files changed, 0 insertions, 0 deletions