[PATCH 08/18] fsmc/nand: Add support for default partitions for several NAND devices
Artem Bityutskiy
dedekind1 at gmail.com
Fri Mar 9 10:11:41 EST 2012
On Fri, 2012-03-09 at 15:47 +0100, Armando Visconti wrote:
> 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.
I thing the default should be "no partitions" instead of a hard-coded
list of partitions tailored to a specific system.
> We are passing them also from platform, and it is possible also
> from cmdline.
Fine, then deleting the defaults should not hurt :-)
--
Best Regards,
Artem Bityutskiy
More information about the linux-mtd
mailing list