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] mx6qsabresd: Add basic support
Date: Sat, 14 Apr 2012 18:00:59 +0200	[thread overview]
Message-ID: <4F899F3B.2080103@denx.de> (raw)
In-Reply-To: <CAOMZO5CBmSMUfGL8UKGaLHaGPrTvhtry-cbxBqY3n2fxAaz6jQ@mail.gmail.com>

Am 14/04/2012 17:28, schrieb Fabio Estevam:
> On Sat, Apr 14, 2012 at 12:24 PM, Fabio Estevam <festevam@gmail.com> wrote:
> 
>> Something like the patch below? (Build tested only - no hardware handy
>> right now)
> 
> Sorry, I meant the patch below:
> 
> --- a/common/cmd_mem.c
> +++ b/common/cmd_mem.c
> @@ -40,6 +40,8 @@
>  #define PRINTF(fmt,args...)
>  #endif
> 
> +DECLARE_GLOBAL_DATA_PTR;
> +
>  static int mod_mem(cmd_tbl_t *, int, int, int, char * const []);
> 
>  /* Display values from last command.
> @@ -656,8 +658,10 @@ int do_mem_mtest (cmd_tbl_t *cmdtp, int flag, int argc, cha
> 
>         if (argc > 1)
>                 start = (ulong *)simple_strtoul(argv[1], NULL, 16);
> -       else
> +       else {
>                 start = (ulong *)CONFIG_SYS_MEMTEST_START;
> +               end = (ulong *)(gd->relocaddr -1 );

Something like this, but not exactly this. After sending my answer I
remembered that the stack is *before* u-boot code, and not after as I
wrote - using gd->relocaddr is wrong. We should subtract the memory
reserve for stack and heap from this value.

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-04-14 16:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 15:28 [U-Boot] [PATCH] mx6qsabresd: Add basic support Fabio Estevam
2012-04-11 19:49 ` Wolfgang Denk
2012-04-11 20:15   ` Fabio Estevam
2012-04-11 21:36     ` Wolfgang Denk
2012-04-13 15:56       ` Fabio Estevam
2012-04-13 16:14         ` Dirk Behme
2012-04-13 22:36           ` Fabio Estevam
2012-04-13 23:04             ` Fabio Estevam
2012-04-14  5:36               ` Dirk Behme
2012-04-14 14:41               ` stefano babic
2012-04-14 15:24                 ` Fabio Estevam
2012-04-14 15:28                   ` Fabio Estevam
2012-04-14 16:00                     ` stefano babic [this message]
2012-04-14 20:15                       ` Wolfgang Denk
2012-04-15  8:56                         ` stefano babic
2012-04-14 20:14                   ` Wolfgang Denk
2012-04-14 20:13                 ` Wolfgang Denk
2012-04-15  9:02                   ` stefano babic
2012-07-11  6:23                     ` Dirk Behme
2012-07-11  8:08                       ` Fabio Estevam
2012-04-12  8:23   ` Marek Vasut
2012-04-12 10:52 ` Stefano Babic
2012-09-11  3:56   ` Fabio Estevam
2012-09-11  4:27     ` stefano babic
2012-09-11  5:39     ` Dirk Behme
2012-09-11 14:43     ` Eric Nelson
2012-09-11 15:07       ` Otavio Salvador
2012-09-11 22:10       ` 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=4F899F3B.2080103@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