Hi Stephen, On 5 May 2015 at 10:12, Stephen Warren <swar...@wwwdotorg.org> wrote: > On 05/05/2015 10:03 AM, Simon Glass wrote: >> >> Hi Stephen, >> >> On 5 May 2015 at 09:59, Stephen Warren <swar...@wwwdotorg.org> wrote: >>> >>> On 05/04/2015 11:31 AM, Simon Glass wrote: >>>> >>>> >>>> We are getting very close to running out of space in SPL, and with the >>>> currently Chrome OS gcc 4.9 we exceed the limit. Add a litle more space. >>> >>> >>> >>> 8K is quite a bump given we only had 24K allocated before. Why is gcc-4.9 >>> less efficient that earlier compilers I wonder? Were we extremely close >>> to >>> the limit ebfore? Still, I guess this is fine.
We were about 1KB away, mostly due to the gcc garbage collection bug I think. The cros compiler seems even worse, not sure why. >>> >>> Did you validate whether tegra-uboot-flasher still works with this >>> change? I >>> think it will since it only cares about the SPL TEXT_BASE and not the >>> main >>> U-Boot TEXT_BASE, but double-checking would be nice. >> >> >> I tested this with USB A-A (tegrarcm). Is that what you mean? > > > Did you just use tegrarcm, or tegra-uboot-flasher? The latter is a wrapper > on top of tegrarcm, and is a bit more involved. See the various READMEs at > https://github.com/NVIDIA/tegra-uboot-flasher-scripts. This doesn't support > any nyan-derived boards yet, but does support Jetson TK1 which I think you > have? Ah, OK. The script at: https://github.com/NVIDIA/tegra-uboot-flasher-scripts/blob/master/tegra-uboot-flasher looks OK to me. It does not have anything hard-coded that I can see. But I have not used it myself. It's kind-of painful that we have all this out-of-tree Tegra stuff (pin mux also) that might break when we change U-Boot. Is there any way to improve this? Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
