aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/x86/xen_domu
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2012-07-25 17:28:32 +0000
committerFelix Fietkau <nbd@openwrt.org>2012-07-25 17:28:32 +0000
commit5832e754fbf502a7d2f2d7bee054eae1b6ad0520 (patch)
tree8a2b915ad4f00fe32ab28753d4b84e53dfaf31aa /target/linux/x86/xen_domu
parentadc2b21be85a6bf34698e9f6ee72e72d8e6f7d03 (diff)
downloadupstream-5832e754fbf502a7d2f2d7bee054eae1b6ad0520.tar.gz
upstream-5832e754fbf502a7d2f2d7bee054eae1b6ad0520.tar.bz2
upstream-5832e754fbf502a7d2f2d7bee054eae1b6ad0520.zip
mtd: fix trx_fixup
With the BRCM47xx image I have built (Linksys E3000), there are additional writes following the completion of "mtd_replace_jffs2" which invalidate the 'trx_fixup' performed by 'mtd_replace_jffs2'. Moving the 'trx_fixup' to somewhere after all writes have completed fixes the problem. I also noticed that 'erasesize' used to compute 'block_offset' in 'mtd_fixtrx' is used before it is computed by 'mtd_check_open'; moving the call to 'mtd_check_open' up a few lines fixes this. Unlike 'mtd_fixtrx', 'trx_fixup' appears to assume that the TRX header is always at offset 0; which may be the cause of the problem described in Ticket #8960. Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 32866
Diffstat (limited to 'target/linux/x86/xen_domu')
0 files changed, 0 insertions, 0 deletions