public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/5] mx35pdk: Provide proper range for memtest
Date: Mon, 13 Feb 2012 08:26:09 +0100	[thread overview]
Message-ID: <4F38BB11.4090709@denx.de> (raw)
In-Reply-To: <1329061116-3471-2-git-send-email-festevam@gmail.com>

On 12/02/2012 16:38, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
> 
> memtest adresses should contain proper DRAM address range.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  include/configs/mx35pdk.h |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/configs/mx35pdk.h b/include/configs/mx35pdk.h
> index 0c62b9f..f2d4112 100644
> --- a/include/configs/mx35pdk.h
> +++ b/include/configs/mx35pdk.h
> @@ -156,8 +156,8 @@
>  #define CONFIG_SYS_MAXARGS	16	/* max number of command args */
>  #define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE /* Boot Argument Buffer Size */
>  
> -#define CONFIG_SYS_MEMTEST_START	0	/* memtest works on */
> -#define CONFIG_SYS_MEMTEST_END		0x10000
> +#define CONFIG_SYS_MEMTEST_START	(PHYS_SDRAM_1 + PHYS_SDRAM_1_SIZE/2)
> +#define CONFIG_SYS_MEMTEST_END		(PHYS_SDRAM_1 + PHYS_SDRAM_1_SIZE)
>  
>  #undef	CONFIG_SYS_CLKS_IN_HZ	/* everything, incl board info, in Hz */
>  
Personally I do not like that the memory test runs taking automatically
the input parameters - even if the test must run automatically, I think
it is better to put the parameters inside a script else to compile them
with U-Boot.

But if we want to change them, why to put the start address at the
middle of RAM ? The mx35pdk can have two banks of RAM, and the second
one will still not tested. What I mean is that it is quite arbitrary
where to set CONFIG_SYS_MEMTEST_START and CONFIG_SYS_MEMTEST_END, and
with the possibility on some boards to have different RAM configurations
this setup should be not decided at compile time.

And setting the end of test at the end of RAM (but this can open a
debate: really the RAM size is computed at runtime with get_ram_size())
will overwrite U-Boot.

Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2012-02-13  7:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 15:38 [U-Boot] [PATCH 1/5] mx31ads: Provide proper range for memtest Fabio Estevam
2012-02-12 15:38 ` [U-Boot] [PATCH 2/5] mx35pdk: " Fabio Estevam
2012-02-13  7:26   ` Stefano Babic [this message]
2012-03-07 10:10   ` Stefano Babic
2012-03-07 12:38     ` Wolfgang Denk
2012-03-07 13:08       ` Stefano Babic
2012-02-12 15:38 ` [U-Boot] [PATCH 3/5] flea3: " Fabio Estevam
2012-03-07 10:10   ` Stefano Babic
2012-03-07 12:39     ` Wolfgang Denk
2012-02-12 15:38 ` [U-Boot] [PATCH 4/5] imx31_litekit: " Fabio Estevam
2012-03-07 10:10   ` Stefano Babic
2012-02-12 15:38 ` [U-Boot] [PATCH 5/5] imx31_phycore: " Fabio Estevam
2012-03-07 10:11   ` Stefano Babic
2012-02-13  7:12 ` [U-Boot] [PATCH 1/5] mx31ads: " Marek Vasut
2012-03-07 10:11 ` Stefano Babic

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=4F38BB11.4090709@denx.de \
    --to=sbabic@denx.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