RAVPower WD-03, Add LZMA Loader

[arrmo]

@xabolcs

Look!

I don't think think this is it, as it's between versions. But I did see that the driver has changed (see the log above). So perhaps!

@xabolcs

And here is another:

Yes, and this is very interesting,

Overlay FS support (how to enable overlay for new device)

df -Th Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 2.0M 2.0M 0 100% /rom tmpfs tmpfs 123.6M 68.0K 123.6M 0% /tmp tmpfs tmpfs 123.6M 40.0K 123.6M 0% /tmp/root overlayfs:/tmp/root overlay 123.6M 40.0K 123.6M 0% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev block info /dev/sdb1: UUID="4f31ca0e-1154-4f82-a032…

I say that because after a clean boot (not sysupgrade), at the start of rootfs => 0x1985, as expected!

00000000  85 19 03 20 0c 00 00 00  b1 b0 1e e4 ff ff ff ff  |... ............|

But, in spite of what the link says (about out of date), I did see (in failsafe),

The JFFS2 mounting code expects a special marker sequence 0xdeadc0de at the beginning of the rootfs_data partition, if this byte sequence is found; the entire rootfs_data partition is erased and reformatted as JFFS2.

So it's saving the file, to the correct place, but telling it to erase!