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-Users] [GIT PULL] [ARM] Please pull fromgit://denx.de/git/u-boot-arm.git
Date: Thu, 16 Aug 2007 11:40:43 +0200	[thread overview]
Message-ID: <20070816094043.1322B246FC@gemini.denx.de> (raw)
In-Reply-To: Your message of "Wed, 15 Aug 2007 13:40:12 +0200." <002c01c7dfdb$280ab250$dcc4af0a@atmel.com>

Dear Ulf,

in message <002c01c7dfdb$280ab250$dcc4af0a@atmel.com> you wrote:
>
> >> include/led.h => seems specific to the at91rm9200dk board only,
> >>                  please move to board directory. Also, the calls to
> >>                  these functions should be handled without #ifdef's
> >>                  in common code. Either use existing functions hooks,
> >>                  or weak references.
> 
> Please explain further.
> What is a weak reference?

See gcc.info,  Node: Function Attributes:

...
`weak'
     The `weak' attribute causes the declaration to be emitted as a
     weak symbol rather than a global. This is primarily useful in
     defining library functions which can be overridden in user code,
     though it can also be used with non-function declarations.
     ...

See for example the implementation of the declaration of
show_boot_progress() in common/main.c and the use of this function all
over the place.

> Which hooks?

You  could  probably  avoid  all  your  own  code  if  you  had  used
show_boot_progress()  instead.  Alternatively  or in combination, you
could and should have used drivers/status_led.c

> >> cpu/arm920t/start.S => I'm surprised to see a lot of intialization
> >>                 code has now been added to the "reset" entry point.
> >>                 Is this by accident, or am I missing something?
> 
> The changes are there to allow you to boot from a dataflash.
> A bootstrap will initialize the SDRAM and copy from the dataflash (or > NAND flash) 
> IIRC: The code avoids reinitialization of stuff which will crash U-Boot.
> (And sets the LED)

I'm afraid I don't understand. We are not talking about  any  startup
code,  but  about the code of the "reset" function, i. e. what casues
the board to reset.

Maybe the code was added to the wrong place in the file?



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
"It is easier to port a shell than a shell script."      - Larry Wall

  reply	other threads:[~2007-08-16  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 15:08 [U-Boot-Users] [GIT PULL] [ARM] Please pull from git://denx.de/git/u-boot-arm.git Peter Pearse
2007-08-14 16:09 ` Wolfgang Denk
2007-08-14 16:45   ` Peter Pearse
2007-08-14 18:39     ` Wolfgang Denk
2007-08-15 11:40     ` [U-Boot-Users] [GIT PULL] [ARM] Please pull fromgit://denx.de/git/u-boot-arm.git Ulf Samuelsson
2007-08-16  9:40       ` Wolfgang Denk [this message]
2007-08-28 16:14         ` Peter Pearse
2007-08-28 22:59           ` [U-Boot-Users] ARM cleanup - was: " 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=20070816094043.1322B246FC@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