From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3 SPL Overflow
Date: Mon, 22 Aug 2016 08:08:52 -0400 [thread overview]
Message-ID: <20160822120852.GA5342@bill-the-cat> (raw)
In-Reply-To: <00df9331-53e7-6d67-8819-624020eba02a@ti.com>
On Mon, Aug 22, 2016 at 10:13:24AM +0530, Lokesh Vutla wrote:
>
>
> On Sunday 21 August 2016 06:15 PM, Tom Rini wrote:
> > On Sun, Aug 21, 2016 at 06:29:42AM -0500, Adam Ford wrote:
> >
> >> Using Git bisect, it appears to me that
> >> a78cd8613204188991c192b8dae2de0aae3b1722 makes "region `.sram'
> >> overflowed by 888 bytes" when I compile for omap3_logic. As I move
> >> forward through the git commits that overflow amount is continuing to
> >> grow.
> >>
> >> Does anyone else with an OMAP3 have this issue?
> >
> > The best solution I have for this at current is a patch that re-works
> > how we use the download image area and compacts the size we reserve for
> > the scratch area to be still much larger than required.
>
> I agree here. Right now the scratch addr space is 4KB. We can reduce it
> to 1KB. Below is the patch that is being used in ti-u-boot to solve this
> issue.
Ah good. That's the same amount I also cut things down to, for all
of the TI platforms that have this setup from ROM.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160822/ca62d4c0/attachment.sig>
next prev parent reply other threads:[~2016-08-22 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 11:29 [U-Boot] OMAP3 SPL Overflow Adam Ford
2016-08-21 12:45 ` Tom Rini
2016-08-22 4:43 ` Lokesh Vutla
2016-08-22 12:08 ` Tom Rini [this message]
2016-08-25 16:02 ` Adam Ford
2016-08-25 23:32 ` Tom Rini
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=20160822120852.GA5342@bill-the-cat \
--to=trini@konsulko.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