Quote:
Originally Posted by hanakomisa
[SIZE="5"]
So now, I'm currently very stumped on what to do next. If I want to continue, I'll probably have to repartition the eMMC, increasing the size of mmcblk0p1 to 440M, and shift all the other partitions (and reducing the size of mmcblk0p4) accordingly. I don't know how I should go about it though.
My current idea is to delete all the partitions except p1 using fdisk in main mode, recreate them again but with the space increase needed for p1 accounted for, reflash p2 with the diags, p3 with local, but I don't know yet what to do with p4 since I would need it to transfer files using USBMS.
|
Bad idea, the bootloader + a few places in Upstart etc expect the partitions to be located at particular memory offsets. Screwing with this without making sure that you've accounted for every instance that they're used is likely to be.. painful.
The important thing is not the overall size of the partition, it's the size of the
contents of the image:
Code:
/dev/loop23 430M 358M 50M 88% /tmp/pw3/mnt
/dev/loop28 341M 302M 32M 91% /tmp/pw2/mnt
You could probably trim away enough fat from the PW3 image by removing the new UI from the image (with appropriate Upstart tweaks to ensure that nothing is
too broken afterwards).
Beware though, even if you can make the image fit, even the old UI will still be somewhat broken on KT2/PW2 - the old UI uses absolute sizes for UI icons meaning that assets taken from PW3 will be hilariously oversized on KT2/PW2. These assets need to be scaled to match the resolutions of the latter devices.
If you're intent on achieving this, save yourself the pain and
see if you can figure out NFS boot - you'll save a lot of time by cutting out the whole "change/flash/test" cycle.