From: chen gong <gong.chen@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] how compilor know where .text section starts from?
Date: Fri, 05 Dec 2008 09:30:13 +0800 [thread overview]
Message-ID: <49388425.4040005@linux.intel.com> (raw)
In-Reply-To: <389deec70812030426p3a15244ahb2620279faebbbd5@mail.gmail.com>
hank peng ??:
> 2008/12/3 Wolfgang Denk <wd@denx.de>:
>> Dear hank.peng <pengxihan@gmail.com>,
>>
>> repl: bad addresses:
>> hank.peng <pengxihan@gmail.com> -- no at-sign after local-part (<)
>>
>> Please fix the mail address you provide in your headers as return
>> address. Either get rid of the dot, or add quotes.
>>
> Fixed, :)
>> In message <389deec70812022235v3f7ebedav57a62bcca04a19f0@mail.gmail.com> you wrote:
>>> I am new to uboot and reading source code, I have a question: how does
>>> compilor know where .text section starts from?
>> It doesn't. The compiler knows not much about the location of
>> segments. That's a matter the linker deals with.
>>
>>> For example, I am using MPC8548CDS, document says .text section begins
>>> from 0xfff8000, but I haven't find this value in u-boot.lds?
>>> So it must be specified in some other place, right?
>> See board/<name>/config.mk
>>
> I see that, so you mean linker will read TEXT_BASE from config.mk.
> Can I specify its value in u-boot.lds?
Sure, of course you can. But you must ensure when CPU boots up, it can
find the correct entrance.
prev parent reply other threads:[~2008-12-05 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 6:35 [U-Boot] how compilor know where .text section starts from? hank.peng
2008-12-03 11:49 ` Wolfgang Denk
2008-12-03 12:26 ` hank peng
2008-12-05 1:30 ` chen gong [this message]
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=49388425.4040005@linux.intel.com \
--to=gong.chen@linux.intel.com \
--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.