From: Maxime Petazzoni <mpetazzoni@mvista.com>
To: vimal singh <vimal.newwork@gmail.com>
Cc: "Pandita, Vikram" <vikram.pandita@ti.com>,
"Singh,
Vimal"
<IMCEAEX-_O=TI_OU=BD_cn=Recipients_cn=x0094262@dlee86.itg.ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Rix, Tom" <trix@ti.com>
Subject: Re: [PATCH] OMAP3: Zoom2: provide default MTD partitions
Date: Tue, 1 Sep 2009 09:12:13 +0200 [thread overview]
Message-ID: <20090901071212.GA4397@mvista.com> (raw)
In-Reply-To: <ce9ab5790909010004y67d3b29nf6ddc4532d390aef@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
* vimal singh <vimal.newwork@gmail.com> [2009-09-01 12:34:26]:
> > Yes, I am aware of the mtdparts command line arguments, which works
> > great. I think a "default", sensible partition layout for the Zoom2
> > would be nice though.
>
> I agree. Keeping it in the mind that mtdparts command line arguments
> will be given higher precedence anyway...
Exactly. I would recommend that your patch gets merged in. Although I'm
a bit curious of the rationale behind a 30M kernel partition?
Also, given a 512MB NAND, we could easily affect 256MB or more to the
system partition (as well as a bit more space for the userdata
partition).
But that's just nitpicking. As we said, mtdparts can be used to take
precedence over the default settings if they don't match the
user/system's needs.
- Maxime
--
Maxime Petazzoni
Linux kernel & software dev
MontaVista Software, Inc
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-09-01 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 11:59 [PATCH] OMAP3: Zoom2: provide default MTD partitions Maxime Petazzoni
2009-08-27 13:46 ` Pandita, Vikram
2009-08-27 14:03 ` vimal singh
2009-08-27 14:08 ` Pandita, Vikram
2009-08-27 14:06 ` Maxime Petazzoni
2009-08-28 16:26 ` Rix, Tom
2009-09-01 7:04 ` vimal singh
2009-09-01 7:12 ` Maxime Petazzoni [this message]
2009-09-01 7:22 ` vimal singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090901071212.GA4397@mvista.com \
--to=mpetazzoni@mvista.com \
--cc=IMCEAEX-_O=TI_OU=BD_cn=Recipients_cn=x0094262@dlee86.itg.ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=trix@ti.com \
--cc=vikram.pandita@ti.com \
--cc=vimal.newwork@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox