public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] Rollback *again* -- 5 patches PLUS 31 patches...
Date: Thu, 11 Apr 2013 12:48:46 -0400	[thread overview]
Message-ID: <5166E96E.90500@ti.com> (raw)
In-Reply-To: <270954750.1682096.1365698015119.JavaMail.root@advansee.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/11/2013 12:33 PM, Beno?t Th?baudeau wrote:
> Hi Albert,
> 
> On Thursday, April 11, 2013 6:30:58 PM, Albert ARIBAUD wrote:
>> Hi Albert,
>> 
>> On Thu, 11 Apr 2013 17:25:34 +0200, Albert ARIBAUD 
>> <albert.u.boot@aribaud.net> wrote:
>> 
>>> Hello,
>>> 
>>> Older toolchain and PPC incompatibilities appeared in the last
>>> two additions to ToT ARM. To avoid non-bisectability, ToT has
>>> been rolled back from abbecf4c87 to ae74b65987. This removes
>>> 
>>> abbecf4 ARM: Fix __bss_start and __bss_end in linker scripts
>>> 
>>> (HIDDEN not known by most binutils 2.22 or older ones)
>>> 
>>> aad17a2 ARM: fix CONFIG_SPL_MAX_SIZE semantics 72c1601
>>> smdk5250, snow: fix CONFIG_SPL_MAX_SIZE semantics 55e46fc
>>> da850evm, da850_am18xxevm: fix CONFIG_SPL_MAX_SIZE semantics 
>>> 0502854 cam_enc_4xx: fix CONFIG_SPL_MAX_SIZE semantics
>>> 
>>> (PPC builds fail because --pad-to receives an expr, not a
>>> constant)
>> 
>> Actually, the failure was not due to this series, but to patch 
>> 16/30 of Beno?t's series. In agreement with Tom, rolling further
>> back, removing the recent TI PR merge and all of Beno?t's
>> series.
>> 
>> Beno?t, can you fix 16/30 wrt PPC building? If you provide
>> branches, I or Tom can do tests.
>> 
>> Once v12 is ready, I'll apply it back, then the TI PR, then the 
>> __bss_end patch, then the SPL max size series, this one list in
>> order to give us time to choose how overall SPL
>> text+data+rodata+BSS size testing should be done.
> 
> OK, I'll do that. I need to know: - which board fails, - where to
> find the toolchain binaries ready to use for PPC (Ubuntu
> package?), - if all other arches have been build-tested in order to
> avoid new issues popping out later.

P1021RDB-PC_NAND fails and I use ELDK 5.2 for a toolchain for PowerPC.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRZuluAAoJENk4IS6UOR1WxeQP/2X5/dNDz2DyMnd6qaSxZMEG
2wlMRkGjOe8vA47R0NzqS5KyUMhwvMZAhebk798lRjqkY/t5cdFy1sXEnWI3kod3
z4j456bpoQpfbctsaqHw0nCDU/HKBW53BDsFIRTA++2obeZ3Ywmj+TQxkefAgBJY
UoyL33yZKC2M+CjeCKMaHJlmBYEkhthLxYn84zedoN/L8RZi66DXQ5QuGitRWZPL
DfewModX/KNvjyjyJNca4fGymT0PtWvB3gS39Kju9qcF9iSp/aTlla5/xdVx1gY5
FvnXheabmp1iNkyKD/783HExBkbVg99aMWJAo8ARc9HfbZwgY8Dlji7hdVWGXPYG
+RWgPwIp4PdKYTZnC5BK/sAHzWAVMv9iOxzkunxSbla9ULMysh1kPD9x+PVECo57
gJ9Eutui9q5NSLSUF/cIx2NXB9977ScYiFvy5+DX7MxytZvjOOQKor99qA9SqSYJ
kiOybsKtlemfR+wAxPy2hGvxf5CUX/Yc6NPk16x74kQ3bZIy+0/Z8hWkGpRTqDY6
jW8jDtDv90YwnDYVEsQBEoCyBjr/5g2a3sOuTUBhYszMTzC+eJVn8nVaMqyiWPpX
DBGMHC0o9pHJva1jVMf7AH7Q/uD4oUVmZRiSNpZ1znct1WU6D3ik/pTbsG+v3wIE
Qa2PbeHT2Y8Pe3uFzFLN
=2cE2
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2013-04-11 16:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 15:25 [U-Boot] [ARM] Rollback *again* -- 5 patches Albert ARIBAUD
2013-04-11 15:49 ` Stephen Warren
2013-04-11 16:37   ` Albert ARIBAUD
2013-04-11 17:59     ` Tom Warren
2013-04-11 18:01       ` Albert ARIBAUD
2013-04-11 18:04         ` Tom Warren
2013-04-11 18:13           ` Albert ARIBAUD
2013-04-12  6:17             ` Albert ARIBAUD
2013-04-11 16:30 ` [U-Boot] [ARM] Rollback *again* -- 5 patches PLUS 31 patches Albert ARIBAUD
2013-04-11 16:33   ` Benoît Thébaudeau
2013-04-11 16:48     ` Albert ARIBAUD
2013-04-11 17:03       ` Tom Rini
2013-04-11 16:48     ` Tom Rini [this message]
2013-04-12  8:27   ` [U-Boot] [ARM] Rollback *again* -- 5 patches PLUS 31 patches... -- FIXED Albert ARIBAUD

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=5166E96E.90500@ti.com \
    --to=trini@ti.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