Quote:
Originally Posted by natemcnutty
Hehe, looks like you had a similar idea as I did. I extended the size of the system partition by 30MB in my tinboot and was finally able to install the modules. It gets further than I did before, but still have some refactoring to do.
Also of interest for the mtdparts commands, I believe the ro option means it is treated as read-only, and if we place a minus before the data partition, it will use the remaining available flash for data. Here is the way I have mine right now:
Code:
mtdparts=msm_nand:0x10000000@0x0(nand),0x01500000@0x04000000(root),0x076C0000@0x05540000(system),-0x06f60000@0x0cc00000(userdata)
I bypassed rootfs entirely by merging stuff from rootfs into initrd. Unfortunately, I'm still ironing out some kinks that were caused by doing that. This is the way that the Vogue currently does it.
Also, I was looking back through IRC logs, and it looks like Wozzer was having issues with data staying on NAND as well.
IRC logs |
Great. Yeah I did notice that "-" thing... But I never tried it out!
Also it does look like the system offset should be 0x05500000 instead of 0x05540000 but this is just how my math worked out... Recheck it for me.
Are you able to keep your data after a reboot?
@ACL
Yes I was doing the same as Nate. But I don't see any reason why you can't mount the rfs to the root mtd1?