Hi John,
May I take up your offer of a hand with overlayfs on top of ubi?
I have in fact managed to get a working overlay + ubi image,
and also a ubifs image. But I still have a few questions:
- Am I right in thinking that there is no way to concatenate the
kernel and ubi image and have them split automatically like with
the squashfs image without ubi?
- Is there any point bothering with a jffs2 image as well, either
on top of ubi or not?
- the two images require different kernel parameters in the 'chosen'
line of the device tree:
ubi.mtd=rootfs_ubi,256 root=/dev/mtdblock8 // for overlayfs
ubi.mtd=rootfs_ubi,256 root=ubi0:rootfs // for ubifs
Is there any way of combining them so that a single device tree
can be used with both images? Passing the parameters from uboot
ought to be one way of dealing with the problem but I believe
that with recent kernels parameters passed in that way just
get clobbered.
- What is the best way to get the get the image onto the target?
nand write from uboot works fine, but you lose the wear levelling
information each time. I have also use tried booting a ramdisk
image first, copying root-overlay.ubi to /tmp, and flashing it
with ubiformat -f. That works too, but is there another option?
Also, I am a little confused about the status of this patch:
http://patchwork.openwrt.org/patch/5110/
You told me it was a "really bad idea" so I was expecting it to be
rejected! But it is appears in patchwork as accepted. Is that a
mistake?
Thanks,
Ben
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
