From: Robin Gilks <robin.gilks@tait.co.nz>
To: MTD mail list <linux-mtd@lists.infradead.org>
Subject: Command line partition support in 2.6
Date: Thu, 09 Nov 2006 14:26:12 +1300 [thread overview]
Message-ID: <455283B4.20300@tait.co.nz> (raw)
Greetings
I'm just moving from a 2.4 to 2.6 kernel and am trying to make sense of
the command line partition support. In 2.4 I added a definition in
maps/physmap.c
struct map_info physmap_map = {
.name = "asif",
.size = CONFIG_MTD_PHYSMAP_LEN,
.buswidth = CONFIG_MTD_PHYSMAP_BUSWIDTH,
.phys = CONFIG_MTD_PHYSMAP_START,
};
and used a kernel command line of the form:
mtdparts=asif:64K(param),3008K(jffs),256K(u-boot),-(kernel)
to partition the flash.
What is the equivalent procedure now? All the documentation seems to
skim over NOR straight into NAND and all the example maps I've looked at
use a fixed partition map rather than a command line one.
I'm sure its really simple but it beats me at the moment!!
Cheers
--
Robin
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
next reply other threads:[~2006-11-09 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 1:26 Robin Gilks [this message]
2006-11-10 0:27 ` Command line partition support in 2.6 Robin Gilks
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=455283B4.20300@tait.co.nz \
--to=robin.gilks@tait.co.nz \
--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