From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] multiple partitions in mtdparts
Date: Wed, 4 Nov 2009 08:14:30 +0100 [thread overview]
Message-ID: <200911040814.33133.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <1257294893.2375.1343441741@webmail.messagingengine.com>
Am Mittwoch 04 November 2009 01:34:53 schrieb myuboot at fastmail.fm:
> Hi,
>
> I am trying to define multiple partitions using mtdparts variable. But I
> can't get it set automatically right.
>
> I defined the set_bootargs as the following:
> set_bootargs=setenv bootargs root=/dev/mtdblock2 rootfs=cramfs,jffs2
> mtdparts=ph
> ysmap-flash.0:256k(u-boot),256k(u-boot-env),7936k(root1),7936k(root2);physmap-fl
> ash.1:16384k(data) console=ttyS0,115200n8
>
> But when I run set_bootargs, I got the following error -
> # run set_bootargs
> Unknown command 'physmap-flash.1:16384k(data)' - try 'help'
> Can someone help me with the correct format on mtdparts? thanks a lot.
>
I don't know the exact format but it looks like the ";" between (root2);physmap-flash1 causes your error?
Dieter
>
> ====================================================
> mtdparts=mtdparts=physmap-flash.0:256k(u-boot),256k(u-boot-env),7936k(root1),793
> 6k(root2);physmap-flash.1:16384k(data)
> boot=run set_bootargs;chpart nor0,${boot_device};fsload
> boot/uImage;bootm
> mtdids=nor0=physmap-flash.0,nor1=physmap-flash.1
> partition=nor0,2
> mtddevnum=2
> mtddevname=root1
> set_bootargs=setenv bootargs root=/dev/mtdblock2 rootfs=cramfs,jffs2
> mtdparts=ph
> ysmap-flash.0:256k(u-boot),256k(u-boot-env),7936k(root1),7936k(root2);physmap-fl
> ash.1:16384k(data) console=ttyS0,115200n8
> bootargs=root=/dev/mtdblock2 rootfs=cramfs,jffs2
> mtdparts=physmap-flash.0:256k(u
> -boot),256k(u-boot-env),7936k(root1),7936k(root2)
>
> Environment size: 847/262140 bytes
> # run set_bootargs
> Unknown command 'physmap-flash.1:16384k(data)' - try 'help'
> #
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2009-11-04 7:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 0:00 [U-Boot] ARM LED weak symbols Tom Rix
2009-11-04 0:00 ` [U-Boot] [PATCH 1/2] ARM Conditionally compile board LED functions Tom Rix
2009-11-04 0:00 ` [U-Boot] [PATCH 2/2] ARM: fix build error with gcc-4.4.2 about inline function declared weak Tom Rix
2009-11-04 0:34 ` [U-Boot] multiple partitions in mtdparts myuboot at fastmail.fm
2009-11-04 7:14 ` Dieter Kiermaier [this message]
2009-11-04 15:35 ` myuboot at fastmail.fm
2009-11-04 15:57 ` Wolfgang Denk
2009-11-05 20:19 ` [U-Boot] [PATCH 2/2] ARM: fix build error with gcc-4.4.2 about inline function declared weak Wolfgang Denk
2009-11-05 20:39 ` Tom
2009-11-05 22:38 ` Wolfgang Denk
2009-11-10 19:34 ` Tom
2009-11-10 22:45 ` Wolfgang Denk
2009-11-12 0:43 ` [U-Boot] ARM pull request Tom
2009-11-15 21:39 ` Wolfgang Denk
2009-11-11 16:53 ` [U-Boot] [PATCH 2/2] ARM: fix build error with gcc-4.4.2 about inline function declared weak Gaye Abdoulaye Walsimou
2009-11-05 20:24 ` [U-Boot] [PATCH 1/2] ARM Conditionally compile board LED functions Wolfgang Denk
2009-11-05 20:47 ` Tom
2009-11-05 22:43 ` Wolfgang Denk
2009-11-05 23:33 ` Tom
2009-11-12 15:17 ` Alessandro Rubini
2009-11-12 15:59 ` Tom
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=200911040814.33133.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--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