From: johns at msli.com <johns@msli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] no mtdparted from U-Boot> prompt
Date: Fri, 21 Dec 2012 10:29:41 -0800 [thread overview]
Message-ID: <1356114581.28896.89.camel@genx> (raw)
In-Reply-To: <50D43318.8090904@atmel.com>
On Fri, 2012-12-21 at 17:59 +0800, Bo Shen wrote:
> Hi Johns,
>
> On 12/21/2012 07:53 AM, johns at msli.com wrote:
> > This is my first post to the list.
> > I am using u-boot-1.3.4 in buildroot-2011.11
> > My device is a at91sam9g20-ek
> > I have a patch adding: include/configs/at91sam9g20ek.h
> > which I gather acts as a config file for u-boot.
> >
> > U-Boot> help
> > does not list mtdparts
> >
> > But my bootargs does use it:
> > bootargs=mem=64M console=ttyS0,115200 mtdparts=atmel_nand:4M(bootstrap/uboot/kernel)ro,60M(rootfs),-(data) root=/dev/mtdblock1 rw rootfstype=jffs2
>
> This mtdparts is defined for Linux kernel NAND driver.
I had the impression there was also an interactive command-line tool for
mtdparts, from the u-boot prompt.
> >
> > Is there a trick to add the mtdparts command?
>
> Yes, you need to add "#define CONFIG_CMD_MTDPARTS" in
>
I added this to include/configs/at91sam9g20ek.h
Now it contains:
#define CONFIG_JFFS2_NAND 1
#define CONFIG_JFFS2_CMDLINE 1
#define CONFIG_CMD_JFFS2
#define CONFIG_CMD_MTDPARTS"
NOTICE: This email may contain confidential information. Please see http://www.meyersound.com/confidential/ for our complete policy.
next prev parent reply other threads:[~2012-12-21 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 23:53 [U-Boot] no mtdparted from U-Boot> prompt johns at msli.com
2012-12-21 9:59 ` Bo Shen
2012-12-21 18:29 ` johns at msli.com [this message]
2012-12-21 22:53 ` John Stile
2012-12-21 23:13 ` Wolfgang Denk
2012-12-22 0:00 ` John Stile
2012-12-22 8:04 ` Anatolij Gustschin
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=1356114581.28896.89.camel@genx \
--to=johns@msli.com \
--cc=u-boot@lists.denx.de \
/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