From: Cam Mayor <cmayor@iders.ca>
To: Jun Sun <jsun@mvista.com>, David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] extend physmap.c to support run-time adding partitions
Date: Wed, 29 Oct 2003 16:57:27 -0600 [thread overview]
Message-ID: <03102916572705.02584@kilauea.iders.ca> (raw)
In-Reply-To: <20031029104546.K30683@mvista.com>
On Wednesday 29 October 2003 12:45, Jun Sun wrote:
> On Wed, Oct 29, 2003 at 11:13:26AM +0000, David Woodhouse wrote:
> >
> > That's nicer. Why multiple physmap_add_partition() calls rather than
> > just a single array passed to physmap_set_map() though?
>
> Hmm, currently partition only matters when CONFIG_MTD_PARTITIONS
> is enabled. I assume this mean sometimes people want to use
> physmap without partitions. True?
Yes. We have a product that partitions physmap (from the kernel command
line), but also uses the unpartitioned physmap base device.
ie. physmap on /dev/mtd0
physmap partitions on /dev/mtd1, /dev/mtd2, etc. sometimes none.
cam
--
Cameron Mayor
Iders Incorporated
next prev parent reply other threads:[~2003-10-29 22:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 1:25 [PATCH] extend physmap.c to support run-time adding partitions Jun Sun
[not found] ` <20031023153307.GA11669@wohnheim.fh-wedel.de>
2003-10-23 17:03 ` Jun Sun
2003-10-23 17:31 ` Jörn Engel
2003-10-23 17:43 ` Jun Sun
2003-10-23 18:15 ` Jörn Engel
2003-10-23 20:04 ` Jun Sun
2003-10-23 23:57 ` Jun Sun
2003-10-28 8:22 ` Holger Schurig
2003-10-29 2:33 ` Jun Sun
2003-10-27 18:17 ` Jun Sun
2003-10-28 10:50 ` David Woodhouse
2003-10-29 2:28 ` Jun Sun
2003-10-29 11:13 ` David Woodhouse
2003-10-29 18:45 ` Jun Sun
2003-10-29 19:32 ` Jörn Engel
2003-10-29 23:15 ` Jun Sun
2003-10-29 22:57 ` Cam Mayor [this message]
2003-10-29 23:13 ` Jun Sun
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=03102916572705.02584@kilauea.iders.ca \
--to=cmayor@iders.ca \
--cc=dwmw2@infradead.org \
--cc=jsun@mvista.com \
--cc=linux-mtd@lists.infradead.org \
/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