From mboxrd@z Thu Jan 1 00:00:00 1970 From: chen gong Date: Fri, 05 Dec 2008 09:30:13 +0800 Subject: [U-Boot] how compilor know where .text section starts from? In-Reply-To: <389deec70812030426p3a15244ahb2620279faebbbd5@mail.gmail.com> References: <389deec70812022235v3f7ebedav57a62bcca04a19f0@mail.gmail.com> <20081203114904.E6DCC834B020@gemini.denx.de> <389deec70812030426p3a15244ahb2620279faebbbd5@mail.gmail.com> Message-ID: <49388425.4040005@linux.intel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de hank peng ??: > 2008/12/3 Wolfgang Denk : >> Dear hank.peng , >> >> repl: bad addresses: >> hank.peng -- 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//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.