From: Sascha Hauer <s.hauer@pengutronix.de>
To: 张忠山 <zzs213@126.com>
Cc: barebox@lists.infradead.org
Subject: Re: bugfix: _barebox_image_size wrong if enable
Date: Thu, 27 Jun 2019 12:30:12 +0200 [thread overview]
Message-ID: <20190627103012.rmsjxp2e46wq5ntv@pengutronix.de> (raw)
In-Reply-To: <1e801d79-ea67-38d2-b38c-dc5a997b723d@126.com>
On Wed, Jun 26, 2019 at 05:39:09PM +0800, 张忠山 wrote:
> >>>
> >>> AFAIR this only happened for linker variables that point to absolute
> >>> addresses. Differences between addresses also worked with the older
> >>> compilers, and I think this is what your patch does:
> >>
> >> No. my patch just for new toolchain. with old toolchain it has no effect,
> >> Because all of the size is zero.
> >>
> >> By using the newer toolchain:
> >> arm-poky-eabi-gcc (GCC) 8.2.0
> >> GNU ld (GNU Binutils) 2.31.1.20180818
> >>
> >> In barebox config file:
> >> CONFIG_TEXT_BASE=0x23e00000
> >> CONFIG_RELOCATABLE=y
> >
> > With CONFIG_RELOCATABLE enabled TEXT_BASE should be 0x0 and this should
> > be enforced by Kconfig dependencies. Which barebox version are you on
> > and which SoC are you compiling for?
>
> I'm using v2016.10.0 and my custom board based \aon friendlyarm-tiny2
This is really old. Please update to something more recent.
Sascha
--
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
prev parent reply other threads:[~2019-06-27 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 13:37 张忠山
2019-06-18 7:46 ` Sascha Hauer
2019-06-18 10:17 ` 张忠山
2019-06-24 3:37 ` 张忠山
2019-06-26 7:20 ` Sascha Hauer
2019-06-26 9:39 ` 张忠山
2019-06-27 10:30 ` Sascha Hauer [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=20190627103012.rmsjxp2e46wq5ntv@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=zzs213@126.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox