diff options
| author | Rafał Miłecki <zajec5@gmail.com> | 2015-04-12 10:20:59 +0000 |
|---|---|---|
| committer | Rafał Miłecki <zajec5@gmail.com> | 2015-04-12 10:20:59 +0000 |
| commit | 503ccc502d98b32a33a196b5cf35b0e324143d27 (patch) | |
| tree | e40d628beb37aa96e1758401c8ac3502275fa79d /target/linux/bcm53xx/patches-3.18/132-ARM-BCM5301X-Ignore-another-BCM4709-specific-fault-c.patch | |
| parent | a62fa2d36554600a1eb828c51aa0a7e5e47e7adc (diff) | |
| download | upstream-503ccc502d98b32a33a196b5cf35b0e324143d27.tar.gz upstream-503ccc502d98b32a33a196b5cf35b0e324143d27.tar.bz2 upstream-503ccc502d98b32a33a196b5cf35b0e324143d27.zip | |
bcm53xx: fix UBI EOF patch to allow sysupgrade after first installation
With previous version of patch info about need of erasing blocks was
stored once per boot. It was breaking in following scenario:
1) First boot after installation (erasing blocks after 0xdeadc0de)
2) Doing sysupgrade (with ubidetach & ubiformat)
3) Attaching UBI again (it caused all blocks to be erased)
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45387
Diffstat (limited to 'target/linux/bcm53xx/patches-3.18/132-ARM-BCM5301X-Ignore-another-BCM4709-specific-fault-c.patch')
0 files changed, 0 insertions, 0 deletions