public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] RFC: create u-boot-common.lds
Date: Sun, 5 Feb 2012 23:27:51 -0500	[thread overview]
Message-ID: <201202052327.53316.vapier@gentoo.org> (raw)
In-Reply-To: <CALButCKjHAKZe6THzEwDo30z1utGv05kxzd2eSxtYv49zNZA_A@mail.gmail.com>

On Sunday 05 February 2012 22:43:33 Graeme Russ wrote:
> On Mon, Feb 6, 2012 at 2:24 PM, Mike Frysinger wrote:
> > it isn't just that.  i don't think a single u-boot.lds for every arch is
> > feasible.  the kernel method allows all the common pieces to be in a
> > common header, and then the arches to expand the specific pieces in the
> > specific order.
> 
> I can't say I'm a fan of the 'common bits' approach - It really does reduce
> the readability of the linker script IMHO. It took me long enough to deal
> with the fact that the lds file is pre-processed for TEXT_BASE ;)

yes, it does make the linker scripts a bit more opaque, but since each arch is 
doing something unique, it's fairly hard to merge them into a single file.  the 
Linux approach represents what we can do in the real world -- get beyond 
board-specific linker scripts and to one linker script per arch.  then the 
vmlinux.lds.h merges a lot of the stuff that can be shared between arches.

i've unified all the board/SoC linker scripts for Blackfin and now there is just 
one -- arch/blackfin/cpu/u-boot.lds.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120205/502d74d8/attachment.pgp>

  reply	other threads:[~2012-02-06  4:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05  3:02 [U-Boot] [PATCH 1/2] RFC: create u-boot-common.lds Troy Kisky
2012-02-05  3:02 ` [U-Boot] [PATCH 2/2] RFC: Let linker create phy array Troy Kisky
2012-02-05  3:38   ` Mike Frysinger
2012-02-05  6:16     ` Dirk Behme
2012-02-05 13:26     ` Albert ARIBAUD
2012-02-05 20:40       ` Mike Frysinger
2012-02-06 20:53         ` Albert ARIBAUD
2012-02-06 18:48     ` Troy Kisky
2012-02-06 19:07       ` Mike Frysinger
2012-02-06 20:17         ` Troy Kisky
2012-02-06 20:56           ` Albert ARIBAUD
2012-02-06 20:57           ` Mike Frysinger
2012-02-06 21:01             ` Albert ARIBAUD
2012-02-07 15:20               ` Mike Frysinger
2012-02-10 19:39                 ` Albert ARIBAUD
2012-02-10 20:32                   ` Mike Frysinger
2012-02-10 20:57                     ` Albert ARIBAUD
2012-02-10 21:41                       ` Mike Frysinger
2012-02-12 14:45                         ` Albert ARIBAUD
2012-02-06 21:44             ` Troy Kisky
2012-02-07 15:21               ` Mike Frysinger
2012-02-05 21:01 ` [U-Boot] [PATCH 1/2] RFC: create u-boot-common.lds Mike Frysinger
2012-02-05 22:07   ` Graeme Russ
2012-02-06  3:24     ` Mike Frysinger
2012-02-06  3:43       ` Graeme Russ
2012-02-06  4:27         ` Mike Frysinger [this message]
2012-02-06  4:34           ` Graeme Russ
2012-02-06  5:48             ` Mike Frysinger

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=201202052327.53316.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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