On Sun, 2015-12-13 at 04:14 +0100, Marek Vasut wrote:
On Sunday, December 13, 2015 at 01:49:06 AM, Chin Liang See wrote:
On Sun, 2015-12-13 at 01:01 +0100, Marek Vasut wrote:
On Sunday, December 13, 2015 at 12:59:48 AM, Chin Liang See wrote:
On Sat, 2015-12-12 at 16:36 +0100, Marek Vasut wrote:
On Saturday, December 12, 2015 at 07:30:46 AM, Chin Liang See
wrote:
[...]
> Can you share the final layout before you roll out > patches ?
Sure, plan to do so but need to away from desk just now.
Here is the old layout 256k(spl) 64k(env) 64k(dtb) 256k(boot) 16m(kernel) 16m(rootfs)
The new one would like this 256k(spl)
I'd say you should just call this u-boot, see above for the rationale.
256k(env) 15872k(boot) 16m(rootfs)
The boot partition can be used as ubi part or raw partition. It contains the linux dtb, u-boot and linux images.
Is that an UBIFS partition ? If so, why don't you just use two UBI volumes ?
For backward compatibility, it can be raw if user want to stick with old way.
If you're breaking the partitioning layout anyway, you don't have to care about the "old way", right ?
Actually this partition can be used as raw partition if user don't want to store zimage and dtb as raw binary.
You should never store raw zImage/dtb in a flash on a production system. This is real bad and can result in a corruption in the future when the system is in the field for a long time. I'd suggest to just use two UBI volumes, one for fitImage and the other for rootfs.
Yup, we are trying to move the raw away by having UBI enabled. I presume when you refer 2 UBI volumes, I presume its still single UBI partition?
Thanks Chin Liang
But the rootfs partition still can be presented to Linux as ubifs.
That's for sure :)
Best regards, Marek Vasut