From: Peter Asemann <peter.asemann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot.lds questions
Date: Wed, 19 Jan 2005 13:03:15 +0100 [thread overview]
Message-ID: <41EE4C83.9020604@web.de> (raw)
I've "successfully" built my u-boot port (it doesn't throw warnings/error).
To do so I just copied some u-boot.lds from some other port.
I know that the u-boot.lds is a linker script that instructs the linker
to put code elements together in some specific way. At least the first
part does so. But the lower parts of the u-boot.lds I copied seem to be
increasingly deep magic. So... what does the u-boot.lds do exactly and
what happens if mine is wrong/broken? And why do I need it anyway?
The built put out the following things in the main directory:
-rwxr-x--- 1234997 Jan 19 12:51 u-boot
-rwxr-x--- 171372 Jan 19 12:51 u-boot.bin
-rw-r----- 94836 Jan 19 12:51 u-boot.map
-rwxr-x--- 514202 Jan 19 12:51 u-boot.srec
there are some parts that probably are important in board/esm (my
board's directory) too:
-rw-r----- 17000 Jan 17 16:05 esm.o
-rw-r----- 17176 Jan 17 16:05 libesm.a
Does that look reasonable/good?
Peter Asemann
next reply other threads:[~2005-01-19 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 12:03 Peter Asemann [this message]
2005-01-19 21:38 ` [U-Boot-Users] u-boot.lds questions 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=41EE4C83.9020604@web.de \
--to=peter.asemann@web.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