diff options
| author | Sergey Ryazanov <ryazanov.s.a@gmail.com> | 2017-10-11 01:07:08 +0300 |
|---|---|---|
| committer | John Crispin <john@phrozen.org> | 2017-12-14 09:29:30 +0100 |
| commit | 1a51241cb1be87a45cac12753a437f786329afc6 (patch) | |
| tree | d288ae4797636105169c8dd4eeab0dd749c795d1 /tools/firmware-utils/src/otrx.c | |
| parent | 4d8a8c80d91e25b98fee5dc7cb298c33b7213b7f (diff) | |
| download | upstream-1a51241cb1be87a45cac12753a437f786329afc6.tar.gz upstream-1a51241cb1be87a45cac12753a437f786329afc6.tar.bz2 upstream-1a51241cb1be87a45cac12753a437f786329afc6.zip | |
firmware-utils: mktplinkfw: fix JFFS2 EOF markers
mktplinkfw/mktplinkfw2 utilities put JFFS2 EOF market only at 64KB
boundary, this could lead to current device configuration lost during
the sysupgrade on a device, which is equpped with flash with the 4KB
erase block size (e.g. TP-Link Archer C20).
This happens when 64KB and 4KB alignments do not match, so the JFFS2
data is written not exactly at the partition beginnig and startup
scripts can not find the JFFS2 during the first boot just after the
sysupgrade.
Fix this by placing additional JFFS2 EOF marker at a 4KB boundary. Also
keep the marker at 64KB intact, so the utilities will produce images
suitable for devices with both 4KB and 64KB erase blocks.
Fixes: 29a2c2ea80441895a2ffe100d854d2b26d5fa606 (add ability to put
jffs2 eof marker into the image)
Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Diffstat (limited to 'tools/firmware-utils/src/otrx.c')
0 files changed, 0 insertions, 0 deletions