public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: S3C64XX: fix timer broken by relocation
Date: Sat, 13 Nov 2010 19:13:01 +0100	[thread overview]
Message-ID: <20101113181301.4ABCA150ADD@gemini.denx.de> (raw)
In-Reply-To: <4CDEC32B.7050309@gmail.com>

Dear Darius Augulis,

In message <4CDEC32B.7050309@gmail.com> you wrote:
> 
> > FWIW, there already is a solution based on statics and post-relocation
> > initialization for orion5x. The principle there is that the timer is not
> > used before calling board_init_r, so we don't need initializing
> > timestamp before relocation.

STOP!!  I don't think we want this.

> in this case it seems like timer must be initialised after relocation.
> But I don't know if it could be correct for all ARM architectures. Maybe
> some of them use timer before relocation.

Indeed. Drivers and other code may want to implement timeouts and the
like, and need at least basic timer services like udelay() and such.

> Global data is good place to store important static variables because
> they are valid before and after relocation and it could be common for
> all architectures. Since we have automatic size calculation of global
> data structure there should not be a problem to add several additional
> bytes specific to every CPU.

We should keep the gd as small as possible, but adinng one or two
integers here is indeed probably the best approach.


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
Always leave room to add an explanation if it doesn't work out.

  reply	other threads:[~2010-11-13 18:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 20:49 [U-Boot] [PATCH] ARM: S3C64XX: fix timer broken by relocation Darius Augulis
2010-11-12  3:10 ` Minkyu Kang
2010-11-12 18:18   ` Darius Augulis
2010-11-12 19:25     ` Albert ARIBAUD
2010-11-13 16:56       ` Darius Augulis
2010-11-13 18:13         ` Wolfgang Denk [this message]
2010-11-13 18:32           ` Albert ARIBAUD
2010-11-22 18:30           ` Darius Augulis

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=20101113181301.4ABCA150ADD@gemini.denx.de \
    --to=wd@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