Re: [PATCH v2] mtd: cmdlinepart: fix the wrong partitions numberwhen truncating occurs
From: Shmulik Ladkani
Date: Sat Aug 25 2012 - 05:40:53 EST
On Sat, 25 Aug 2012 05:26:51 -0400 Huang Shijie <shijie8@xxxxxxxxx> wrote:
> > The specified cmdline partitions might not be ordered (according to
> > start offset), so next partition specified after the truncated one might
> > define a partition at the beginning of the device, which is okay
> > (regardless the truncation of current partition).
> could you please give me an example of this specified cmdline?
Assume we have a 1GB(8Gb) nand chip:
#gpmi-nand:1g@200m(rootfs),100m@0(boot),100m@100m(kernel)
I am used to explicitly specify size@offset for all my parts.
Obviously I won't define a partition above the device size... somewhat
hypothetical discussion here...
But your code will stop after creating 'rootfs' (and original code will
not create a single partition).
Is that what we want?
Or do we want to truncate 'rootfs', but still have the valid 'boot' and
'kerner' partitions?
Regards,
Shmulik
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/