From: Alexander Aring <alex.aring@gmail.com>
To: Kevin Du Huanpeng <u74147@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: barebox.lds.S, why _edata not follows the end of .data section?
Date: Mon, 14 Oct 2013 15:48:52 +0200 [thread overview]
Message-ID: <20131014134851.GA7556@omega> (raw)
In-Reply-To: <CANvTkNZOQZt=XcYxSPX0+jT7tK9PrradDwWEcTtCfOQi1c9boQ@mail.gmail.com>
Hi,
On Mon, Oct 14, 2013 at 09:02:49PM +0800, Kevin Du Huanpeng wrote:
> Hi, in the linker script,
> > _sdata = .;
> >. = ALIGN(4);
> > .data : { *(.data*) }
> ? why _edata is not here?
Yes it could be there. I added this to the linker script because I
needed all sdram_regions for barebox to jump over all barebox memory
regions in memtest.
Another solution would be to add a another region for barebox_cmds or
something else, but I though that can be located in data, too.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-10-14 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 13:02 barebox.lds.S, why _edata not follows the end of .data section? Kevin Du Huanpeng
2013-10-14 13:48 ` Alexander Aring [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=20131014134851.GA7556@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=u74147@gmail.com \
/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.