mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Aring <a.aring@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH/RFC 3/4] barebox-data: add barebox-data sections
Date: Tue, 6 Mar 2012 09:50:32 +0100	[thread overview]
Message-ID: <20120306085032.GF3852@pengutronix.de> (raw)
In-Reply-To: <1330700647-27368-3-git-send-email-a.aring@phytec.de>

On Fri, Mar 02, 2012 at 04:04:06PM +0100, Alexander Aring wrote:
> Add barebox-data section in arm branch to get complete
> barebox regions in sdram regions tree.
> 
> Signed-off-by: Alexander Aring <a.aring@phytec.de>
> ---
> It's right here to decrement the end adresses? Otherwise sdram
> regions will overlap.

Yes, that's correct.

> I only add this to arm, because I don't much about others
> architectures.
> So please help me to add a data region for others architectures.

It should be between _etext and __bss_start for all other architectures
aswell.

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

       reply	other threads:[~2012-03-06  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1330700647-27368-1-git-send-email-a.aring@phytec.de>
     [not found] ` <1330700647-27368-3-git-send-email-a.aring@phytec.de>
2012-03-06  8:50   ` Sascha Hauer [this message]
     [not found] ` <1330700647-27368-4-git-send-email-a.aring@phytec.de>
2012-03-06  9:05   ` [PATCH/RFC 4/4] memtest: rewrite memtest commands Sascha Hauer

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=20120306085032.GF3852@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.aring@phytec.de \
    --cc=barebox@lists.infradead.org \
    /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