public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: sun york-R58495 <R58495@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 8/8] powerpc/85xx: Add memory test feature for mpc85xx.
Date: Wed, 28 Jul 2010 18:25:00 -0500	[thread overview]
Message-ID: <516c01cb2eac$1d67cdf1$0c23400a@fsl.freescale.net> (raw)

Wolfgang,

As Timur pointed out, the post framework doesn't work for us. After U-boot relocate itself to RAM, we have only 2GB memory to test. The best place is before relocation. Many other boards do that. Following your idea of reusing code, I can only reuse the test pattern generator. I am open to suggestions.

York Sun
----- Original Message -----
From:"Wolfgang Denk" <wd@denx.de>
To:"York Sun" <yorksun@freescale.com>
Cc:"Timur Tabi" <timur.tabi@gmail.com>, "Kumar Gala" <galak@kernel.crashing.org>, "u-boot at lists.denx.de" <u-boot@lists.denx.de>
Sent:7/28/2010 4:50 PM
Subject:Re: [U-Boot] [PATCH 8/8] powerpc/85xx: Add memory test feature for mpc85xx.


Dear York Sun,

In message <1280351179.8571.63.camel@oslab-l1> you wrote:
> 
> > We already have too many different implementations of a memory test in
> > U-Boot, and I will not accept adding yet another one.
> > 
> I can reuse your testing code but have to move the desired code out of
> memory.c file to avoid the need for CONFIG_POST and
> CONFIG_SYS_POST_MEMORY. I also add a progress indicator. My testing

NAK, and NAK.

Please integrate your code into the existing POST framework instead,
as a number of other boards already did.

A progress indicator may be a nice little toy, but how does it
integrate into the POST framework?

> target is 2GB at a time, up to physically memory size which is easily
> over 8GB. Without progress indicator, it feels hung when it is actually
> running.

Yes, memory testing takes time. In the context of a power-on self
test (and this is what you are doing, right?) we should take care to
fit it into the existing framework, though.

> Please take a look at the patch below.

Instead of integrating your needs into an existing framework you
invent yet another one. I don't want to have this, sorry.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
How can you tell when sour cream goes bad?

             reply	other threads:[~2010-07-28 23:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 23:25 sun york-R58495 [this message]
2010-07-29 21:28 ` [U-Boot] [PATCH 8/8] powerpc/85xx: Add memory test feature for mpc85xx Wolfgang Denk
2010-07-30 21:20   ` [U-Boot] help on POST York Sun
2010-07-30 21:29     ` Wolfgang Denk
2010-07-30 21:34       ` York Sun
2010-07-31 17:11         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2010-07-14 15:14 [U-Boot] [PATCH 1/8] powerpc/8xxx: Enabled hwconfig for memory interleaving Kumar Gala
2010-07-14 15:14 ` [U-Boot] [PATCH 2/8] powerpc/8xxx: Fix bug in memctrl interleaving & bank interleaving on cs0~cs4 Kumar Gala
2010-07-14 15:14   ` [U-Boot] [PATCH 3/8] powerpc/8xxx: Enable quad-rank DIMMs Kumar Gala
2010-07-14 15:14     ` [U-Boot] [PATCH 4/8] powerpc/8xxx: Enabled address hashing for 85xx Kumar Gala
2010-07-14 15:14       ` [U-Boot] [PATCH 5/8] powerpc/8xxx: Enable DDR3 RDIMM support Kumar Gala
2010-07-14 15:15         ` [U-Boot] [PATCH 6/8] powerpc/8xxx: Improvement to DDR parameters Kumar Gala
2010-07-14 15:15           ` [U-Boot] [PATCH 7/8] powerpc/p2020ds: Integrated with P2020DS DDR change and enabled hwconfig Kumar Gala
2010-07-14 15:15             ` [U-Boot] [PATCH 8/8] powerpc/85xx: Add memory test feature for mpc85xx Kumar Gala
2010-07-14 20:16               ` Wolfgang Denk
2010-07-14 22:13                 ` Timur Tabi
2010-07-15  9:07                   ` Wolfgang Denk
2010-07-28 21:06                     ` York Sun
2010-07-28 21:50                       ` Wolfgang Denk

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='516c01cb2eac$1d67cdf1$0c23400a@fsl.freescale.net' \
    --to=r58495@freescale.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