On Monday, December 14, 2015 at 08:54:38 AM, Pavel Machek wrote:
(Please, trim your emails when replying)
On Mon 2015-12-14 01:58:04, Marek Vasut wrote:
On Monday, December 14, 2015 at 01:43:58 AM, Chin Liang See wrote:
On Mon, 2015-12-14 at 01:22 +0100, Marek Vasut wrote:
On Monday, December 14, 2015 at 01:11:27 AM, Chin Liang See wrote:
On Sun, 2015-12-13 at 16:42 +0100, Marek Vasut wrote:
On Sunday, December 13, 2015 at 02:03:02 PM, Chin Liang See
After grabbing a coffee
That's a good idea, though I think I will make do with a green tea (抹茶).
and rethinking, we can have 2 MTD_PARTITION where one for backward compatiblity (supporting raw) while another for UBI.
MTDPARTS_RAW 256k(spl), 256k(env), 15872k(boot), -(rootfs)
MTDPARTS_UBI 256k(spl), 256k(env), -(UBI)
We should make UBI as default then. If user care about backward compatiblity, they shall use the MTDPARTS_RAW then.
Try this:
mtdparts=1m(u-boot),256k(env1),256k(env2),14848k(boot),112m(root),-@1536k (UBI)
This will create overlapping partitions "boot,root" and "UBI" .
Just because you can does not mean that you should. This looks like a nasty trap for a user.
Please explain in detail why do you think so.
Best regards, Marek Vasut