[PATCH 08/18] fsmc/nand: Add support for default partitions for several NAND devices
Armando Visconti
armando.visconti at st.com
Fri Mar 9 09:47:57 EST 2012
On 03/09/2012 02:07 PM, Artem Bityutskiy wrote:
> On Wed, 2012-03-07 at 17:00 +0530, Vipin Kumar wrote:
>> +static struct mtd_partition partition_info_64KB_blk[] = {
>> + {
>> + .name = "X-loader",
>> + .offset = 0,
>> + .size = 4*0x10000,
>> + },
>> + {
>> + .name = "U-Boot",
>> + .offset = 4*0x10000,
>> + .size = 8*0x40000,
>> + },
>> + {
>> + .name = "Kernel",
>> + .offset = (4+8)*0x10000,
>> + .size = 64*0x40000,
>> + },
>> + {
>> + .name = "Root File System",
>> + .offset = (4+8+64)*0x10000,
>> + .size = MTDPART_SIZ_FULL,
>> + },
>> +};
>
> Shouldn't this kind of data come from DT/platform data or cmdline
> instead? Does it make sense to have it hard-coded in the driver?
>
These are just the default partitions.
We are passing them also from platform, and it is possible also
from cmdline.
But in case we don't, this is the default.
Shouldn't we treat such a case?
Ciao,
Arm
More information about the linux-mtd
mailing list