public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] post memory test
Date: Mon, 19 Nov 2007 08:55:26 +0100	[thread overview]
Message-ID: <4741416E.1040707@tqs.de> (raw)
In-Reply-To: <20071116192117.42A7224887@gemini.denx.de>

Wolfgang Denk schrieb:
> In message <473D9B54.1010304@tqs.de> you wrote:
>>> As an example look at initdram() in board/Marvell/db64460/sdram_init.c
>>> where the platform uses Block Address Translations (BATs) to map RAM
>>> but exhausts these pretty scarce ressources and limits itself to
>>> mapping only the first 256MB (a usual limit for a BAT).
>> So it is possible to overlay the function memory_post_test() by a
>> board specific routine, which may cover almost all RAM?
> 
> Everything is possible - this is software, so anything can be done.
> You can even make pigs fly. But not everything does make sense.
> 
>> BTW, is it possible to overlay _all_ POST routines by board specific
>> routines?
> 
> It could be done, but I consider it a very, very bad idea.
> 
> Best regards,
> 
> Wolfgang Denk
> 
And what if the tests wouldn't meet certain requirements of the
developer or customer or if it had to be adapted to CPU- or
board-specific conditions?
I suppose, you wouldn't like much "#ifdef <CPU>"s or "#ifdef <board>"s
in common code.
Could you please make a proposal to solve this and to get such code
into the official U-Boot tree?

Kind regards
    Jens

  reply	other threads:[~2007-11-19  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 23:50 [U-Boot-Users] post memory test Dongying_Xu at us.alphanetworks.com
2007-11-14 11:02 ` Detlev Zundel
2007-11-16 13:29   ` Jens Gehrlein
2007-11-16 19:21     ` Wolfgang Denk
2007-11-19  7:55       ` Jens Gehrlein [this message]
2007-11-19 13:13         ` Wolfgang Denk
2007-11-19 15:34         ` Detlev Zundel

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=4741416E.1040707@tqs.de \
    --to=sew_s@tqs.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