All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Roth <mroth@nessie.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Allow board specific overwriting of library code
Date: Wed, 04 Feb 2009 17:00:14 +0100	[thread overview]
Message-ID: <4989BB8E.9090405@nessie.de> (raw)
In-Reply-To: <20090204153632.231B48322908@gemini.denx.de>

Wolfgang Denk schrieb:

> Why would that be needed?

Because the whole weak-linking looks like it is somewhat broken or at
least very difficult to get it correctly.


> Normally you deal with such issues in your linker script, i. e. in a
> board specific way without need to modify global files.

Yes, there are several possible solutions to address this issue. Until
now, there were discussed: CONFIG_XYZ and ifdef/endif and pre-build
objects (patch from Jean-Christophe) and my proposal.

Using a board specific linker script is another way.

However, because the problem regarding weak-linking is a global one,
maybe the circumvention should be global too.

But I don't know. I could also use a board specific linker script.


Michael Roth


(Email resend because of stupid user error by my...)

  reply	other threads:[~2009-02-04 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 14:29 [U-Boot] [PATCH 0/2] Initial Stamp9261 board support Michael Roth
2009-02-04 14:29 ` [U-Boot] [PATCH 1/2] Allow board specific overwriting of library code Michael Roth
2009-02-04 14:29   ` [U-Boot] [PATCH 2/2] Stamp9261 board support Michael Roth
2009-02-04 16:05     ` Wolfgang Denk
2009-02-05 14:07       ` Michael Roth
2009-02-04 14:48   ` [U-Boot] [PATCH 1/2] Allow board specific overwriting of library code Jerry Van Baren
2009-02-04 15:36   ` Wolfgang Denk
2009-02-04 16:00     ` Michael Roth [this message]
2009-02-04 16:08       ` Wolfgang Denk
2009-02-04 16:18       ` Michael Roth
2009-02-04 16:23         ` Mike Frysinger
2009-02-04 21:12         ` 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=4989BB8E.9090405@nessie.de \
    --to=mroth@nessie.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 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.