All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [TEST] arm:board_init_f(): mirror BSS and check after each	init_fnc()
Date: Wed, 01 Dec 2010 13:12:19 +0100	[thread overview]
Message-ID: <4CF63BA3.6020603@gmail.com> (raw)
In-Reply-To: <4CF63345.9020006@free.fr>

Dear Albert ARIBAUD,

Am 01.12.2010 12:36, schrieb Albert ARIBAUD:
> hi Andreas,
> 
> Le 01/12/2010 11:05, Andreas Bie?mann a ?crit :
> 
>> I can not recommend a proper place for all boards cause this parameter
>> is highly is board specific.
> 
> Understood -- each board maintainer must select an adapted location for
> the mirror.

Yes, but I have one thing to mention. This test does only detect writing
to BSS values in one of the init_sequence[] functions.

In my case I detected arch/arm/cpu/arm920t/at91/timer.c as faulty. But I
still have some issues booting at91rm9200ek from NOR flash. None of the
init_sequence[] functions writes to a BSS value in that case ... So if
the 'corrupted .dyn.rel' thing is my problem in NOR booting case
.dyn.rel got corrupted before board_init_f() or by some other function
call between for loop of init_sequence[] and relocate_code() ... I don't
know if I get this until release of v2010.12.

Maybe another maintainer is more lucky ...

regards

Andreas Bie?mann

  reply	other threads:[~2010-12-01 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  8:10 [U-Boot] [TEST] arm:board_init_f(): mirror BSS and check after each init_fnc() Andreas Bießmann
2010-12-01  9:37 ` Albert ARIBAUD
2010-12-01 10:05   ` Andreas Bießmann
2010-12-01 11:36     ` Albert ARIBAUD
2010-12-01 12:12       ` Andreas Bießmann [this message]
2010-12-01 12:27         ` Albert ARIBAUD
2010-12-01 12:35       ` Wolfgang Denk
2010-12-01 12:47         ` Albert ARIBAUD

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=4CF63BA3.6020603@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.