From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] ARM: sheevaplug: correct nand partition layout
Date: Tue, 19 Jan 2016 12:14:23 -0500 [thread overview]
Message-ID: <20160119171423.GI3359@bill-the-cat> (raw)
In-Reply-To: <1453051425-392-5-git-send-email-peter@korsgaard.com>
On Sun, Jan 17, 2016 at 06:23:45PM +0100, Peter Korsgaard wrote:
> Commit 1e3d640316 (ARM: sheevaplug: redefine MTDPARTS) changed the partition
> layout (without any description why), but didn't change the offset/size to
> load the kernel from or the root=/dev/mtdblockX in the bootargs.
>
> The 3MB forseen for a kernel is furthermore too little. A 4.4 build of
> mvebu_v5_defconfig is 3.6MB:
>
> -rw-r--r-- 1 peko peko 3.6M Jan 16 20:24 uImage.kirkwood-sheevaplug
>
> When device tree support for sheevaplug was added to the kernel in commit
> ee514b381e (ARM: Kirkwood: Add dts files for Sheevaplug and eSATA
> Sheevaplug) a default flash partition layout (used if mtdparts= isn't passed
> on the command line / CONFIG_MTD_CMDLINE_PARTS isn't enabled) with 1MB for
> u-boot / environment, 4MB for the kernel and the rest for the rootfs, so use
> that layout here and adjust the kernel loading to match.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> include/configs/sheevaplug.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/configs/sheevaplug.h b/include/configs/sheevaplug.h
> index c529636..f9fb9bc 100644
> --- a/include/configs/sheevaplug.h
> +++ b/include/configs/sheevaplug.h
> @@ -64,12 +64,12 @@
>
> #define CONFIG_MTDPARTS \
> "orion_nand:512K(uboot)," \
> - "512K(env),1M(script),6M(kernel)," \
> - "12M(ramdisk),4M(spare),-(rootfs)\0"
> + "512K(env),4M(kernel)," \
> + "-(rootfs)\0"
>
> #define CONFIG_EXTRA_ENV_SETTINGS "x_bootargs=console" \
> "=ttyS0,115200 mtdparts="CONFIG_MTDPARTS \
> - "x_bootcmd_kernel=nand read 0x6400000 0x100000 0x300000\0" \
> + "x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000\0" \
> "x_bootcmd_usb=usb start\0" \
> "x_bootargs_root=root=/dev/mtdblock3 rw rootfstype=jffs2\0"
Can I suggest future proofing this by using the names set in MTDPARTS
instead of direct offsets? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160119/bde1ff79/attachment.sig>
next prev parent reply other threads:[~2016-01-19 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 17:23 [U-Boot] [PATCH 0/4] ARM: sheevaplug: misc fixes Peter Korsgaard
2016-01-17 17:23 ` [U-Boot] [PATCH 1/4] ARM: sheevaplug: unbreak default environment Peter Korsgaard
2016-01-17 17:23 ` [U-Boot] [PATCH 2/4] ARM: sheevaplug: unbreak kernel bootargs / mtdparts command by dropping double mtdparts= Peter Korsgaard
2016-01-17 17:23 ` [U-Boot] [PATCH 3/4] ARM: sheevaplug: drop unneded 'usb start' from boot command Peter Korsgaard
2016-01-17 17:23 ` [U-Boot] [PATCH 4/4] ARM: sheevaplug: correct nand partition layout Peter Korsgaard
2016-01-19 17:14 ` Tom Rini [this message]
2016-01-19 17:48 ` Peter Korsgaard
2016-03-24 8:26 ` Stefan Roese
2016-01-17 21:59 ` [U-Boot] [PATCH 0/4] ARM: sheevaplug: misc fixes Luka Perkov
2016-03-14 22:08 ` Peter Korsgaard
2016-03-14 22:34 ` Luka Perkov
2016-03-14 22:37 ` Peter Korsgaard
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=20160119171423.GI3359@bill-the-cat \
--to=trini@konsulko.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