public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] ARM: at91 series: increase size for u-boot and change bootargs
Date: Mon, 26 Nov 2012 11:59:57 +0100	[thread overview]
Message-ID: <50B34BAD.3020001@gmail.com> (raw)
In-Reply-To: <1352771881-25772-1-git-send-email-voice.shen@atmel.com>

Dear Bo Shen,

On 13.11.2012 02:58, Bo Shen wrote:
> As to more features are added into the u-boot, which cause the u-boot
> size larger than 0x40000 (256KiB), so increase the size for u-boot
> through move offset of the u-boot environment. Or else, when execute
> saveenv command, which will erase the end of the u-boot causing it can
> not boot up again.
> 
> Also, the linux kernel image is bigger than 2MiB, so change the bootcmd
> as the same time.
> 
> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> ---
> Change since v1:
>   change the bootargs as to the size of mainline linux kernel image size
> ---
>  include/configs/at91sam9260ek.h    |   17 ++++++++---------
>  include/configs/at91sam9261ek.h    |   17 ++++++++---------
>  include/configs/at91sam9263ek.h    |   15 ++++++++-------
>  include/configs/at91sam9m10g45ek.h |   15 +++++++--------
>  4 files changed, 31 insertions(+), 33 deletions(-)
> 
> diff --git a/include/configs/at91sam9260ek.h b/include/configs/at91sam9260ek.h
> index f921fac..905d5c5 100644
> --- a/include/configs/at91sam9260ek.h
> +++ b/include/configs/at91sam9260ek.h
> @@ -210,16 +210,15 @@
>  
>  /* bootstrap + u-boot + env + linux in nandflash */
>  #define CONFIG_ENV_IS_IN_NAND	1
> -#define CONFIG_ENV_OFFSET		0x60000
> -#define CONFIG_ENV_OFFSET_REDUND	0x80000
> +#define CONFIG_ENV_OFFSET		0xc0000
> +#define CONFIG_ENV_OFFSET_REDUND	0x100000
>  #define CONFIG_ENV_SIZE		0x20000		/* 1 sector = 128 kB */
> -#define CONFIG_BOOTCOMMAND	"nand read 0x22000000 0xA0000 0x200000; bootm"
> -#define CONFIG_BOOTARGS		"console=ttyS0,115200 "			\
> -				"root=/dev/mtdblock5 "			\
> -				"mtdparts=atmel_nand:128k(bootstrap)ro,"	\
> -				"256k(uboot)ro,128k(env1)ro,"		\
> -				"128k(env2)ro,2M(linux),-(root) "	\
> -				"rw rootfstype=jffs2"
> +#define CONFIG_BOOTCOMMAND	"nand read 0x22000000 0x200000 0x300000; bootm"
> +#define CONFIG_BOOTARGS							\
> +	"console=ttyS0,115200 earlyprintk "				\
> +	"mtdparts=atmel_nand:"						\
> +	"8M(bootstrap/uboot/kernel)ro,-(rootfs) "			\
> +	"root=/dev/mtdblock1 rw rootfstype=jffs2"

I personally prefer to change bootlaoder related stuff also from linux.
With this change you can not access the env partition from linux
therefore you can never use tools like fw_pritnenv/fw_setenv.
Can you please change this to a reasonable configuration. I think
current setups will require about 1 sector for bootstrap, 1 or 2 sectors
for each env, about 4 to 6 sectors for u-boot, another bunch of sectors
for linux and maybe some place to store a configuration blob (think of
'Falcon mode' or FDT).

Best regards

Andreas Bie?mann

  reply	other threads:[~2012-11-26 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  1:58 [U-Boot] [PATCH v2] ARM: at91 series: increase size for u-boot and change bootargs Bo Shen
2012-11-26 10:59 ` Andreas Bießmann [this message]
2012-11-27  1:28   ` Bo Shen

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=50B34BAD.3020001@gmail.com \
    --to=andreas.devel@googlemail.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