public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug in buildsystem for SPL LDSCRIPT
Date: Wed, 09 Apr 2014 08:31:53 +0200	[thread overview]
Message-ID: <5344E959.1080606@gmail.com> (raw)
In-Reply-To: <20140409112705.0A13.AA925319@jp.panasonic.com>

Hi Masahiro,

On 04/09/2014 04:27 AM, Masahiro Yamada wrote:
> On Mon, 07 Apr 2014 11:35:07 +0200
> "Andreas Biesmann" <andreas.devel@googlemail.com> wrote:
> 
>> and also to the list ... sorry for the noise
>>
>> On 04/07/2014 11:27 AM, Andreas Biesmann wrote:
>>> Hi Masahiro,
>>>
>>> a late bug report ;) changing my board config file will not regenerate
>>> the spl/u-boot-spl.lds for the board though it depends on it. The
>>> LDSCRIPT is patched with some size information for range checking which
>>> is not updated in my case. However regenerating the file by deleting it
>>> first works. Cold you please provide a fix for that in 2014.04?
> 
> Could you give me an example in which spl/u-bool-spl.lds is not
> correctly regenerated.


it is not regenerated when the configuration is changed. Here is my use
case:

---8<---
abiessmann at punisher % git describe
v2014.04-rc3-91-g36490ee
abiessmann at punisher % PATH=$ARMa8_PATH:$PATH make O=/tmp/tricorder
ARCH=arm CROSS_COMPILE=arm-cortexa8-linux-gnueabi- -j16 -s
tricorder_config all
Configuring for tricorder board...
PATH=$ARMa8_PATH:$PATH make O=/tmp/tricorder ARCH=arm  -j16 -s  all
27.23s user 2.47s system 539% cpu 5.507 total
abiessmann at punisher % grep CONFIG_SPL_MAX_SIZE include/configs/tricorder.h
#define CONFIG_SPL_MAX_SIZE		(57 * 1024)	/* 7 KB for stack */
abiessmann@punisher % head -1 /tmp/tricorder/spl/u-boot-spl.lds
MEMORY { .sram : ORIGIN = 0x40200000, LENGTH = (57 * 1024) }
--->8---


... modify configuration

---8<---
abiessmann at punisher % grep CONFIG_SPL_MAX_SIZE include/configs/tricorder.h
#define CONFIG_SPL_MAX_SIZE		(59 * 1024)	/* 7 KB for stack */
abiessmann at punisher % PATH=$ARMa8_PATH:$PATH make O=/tmp/tricorder
ARCH=arm CROSS_COMPILE=arm-cortexa8-linux-gnueabi- -j16 -s all
PATH=$ARMa8_PATH:$PATH make O=/tmp/tricorder ARCH=arm  -j16 -s all
25.25s user 2.16s system 550% cpu 4.974 total
abiessmann at punisher % head -1 /tmp/tricorder/spl/u-boot-spl.lds
MEMORY { .sram : ORIGIN = 0x40200000, LENGTH = (57 * 1024) }
abiessmann at punisher % ls -l /tmp/tricorder/spl/u-boot-spl.lds
-rw-r--r-- 1 abiessmann abiessmann 699 Apr  9 08:27
/tmp/tricorder/spl/u-boot-spl.lds
abiessmann at punisher % ls -l /tmp/tricorder/spl/u-boot-spl
-rwxr-xr-x 1 abiessmann abiessmann 571948 Apr  9 08:28
/tmp/tricorder/spl/u-boot-spl*
abiessmann at punisher % ls -l include/configs/tricorder.h
-rw-r--r-- 1 abiessmann abiessmann 12071 Apr  9 08:28
include/configs/tricorder.h
abiessmann@punisher %
--->8---

Best regards

Andreas Bie?mann

  reply	other threads:[~2014-04-09  6:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53426F8C.3050007@gmail.com>
2014-04-07  9:35 ` [U-Boot] Bug in buildsystem for SPL LDSCRIPT Andreas Bießmann
2014-04-09  2:27   ` Masahiro Yamada
2014-04-09  6:31     ` Andreas Bießmann [this message]
2014-04-09 11:13       ` Masahiro Yamada
2014-04-09 11:21         ` Andreas Bießmann

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=5344E959.1080606@gmail.com \
    --to=andreas.devel@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox