From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 6/8] omap3_beagle: add nand_spl support
Date: Wed, 29 Dec 2010 11:07:08 +0530 [thread overview]
Message-ID: <4D1AC904.6020808@ti.com> (raw)
In-Reply-To: <AANLkTin-qX_sxscmJ27zGAWn7EZp=tt2+MLUyW6WGwRa@mail.gmail.com>
On Wednesday 29 December 2010 05:56 AM, John Rigby wrote:
> On Mon, Dec 27, 2010 at 11:50 PM, Aneesh V<aneesh@ti.com> wrote:
>> Hello John,
>>
>> On Tuesday 28 December 2010 06:17 AM, John Rigby wrote:
>> < snip>
>>
>>> +LDSCRIPT= $(TOPDIR)/nand_spl/board/$(BOARDDIR)/u-boot.lds
>>> +LDFLAGS = -Bstatic -T $(nandobj)u-boot.lds -Ttext $(CONFIG_SYS_NAND_SPL_TEXT_BASE) $(PLATFORM_LDFLAGS)
>>> +AFLAGS += -DCONFIG_PRELOADER -DCONFIG_NAND_SPL
>>> +CFLAGS += -DCONFIG_PRELOADER -DCONFIG_NAND_SPL
>>
>> How big is the spl now? For the OMAP4 spl, using '-ffunction-sections'
>> and '--gc-sections' reduced the image size by 40% and helped it fit
>> into the SRAM bugdet. I am sure your nand_spl is already fitting in the
>> SRAM bugdet. But these flags may help reduce the size further. Do you
>> want to try it?
> It is about 12K. I will try the additional flags and see what
That's impressive. I think you won't need those flags then. the MMC spl
for OMAP4 was much bigger(37 KB without --gc-sections and 22 KB with
--gc-sections). I think the main difference is that for MMC spl I am
using the u-boot MMC driver where as for nand spl you seem to be using
a driver tailor made for the spl.
BTW, Is there a good way to know the contribution of each file/function
to the final image size. I couldn't find any suitable option in 'ld'.
With RVCT this was much easier.
next prev parent reply other threads:[~2010-12-29 5:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 0:47 [U-Boot] [RFC PATCH 0/8] Add nand_spl support for TI OMAP Beagle John Rigby
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 1/8] NAND: nand_spl/nand_boot.c: add 16-bit and readid support John Rigby
2011-01-04 22:08 ` Scott Wood
2011-01-04 22:19 ` Scott Wood
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 2/8] armv7: add nand_spl support John Rigby
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 3/8] OMAP3: and " John Rigby
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 4/8] OMAP3: add dram timing constants from x-loader John Rigby
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 5/8] NAND: omap_gpmc.c: add nand_spl support John Rigby
2011-01-04 22:24 ` Scott Wood
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 6/8] omap3_beagle: " John Rigby
2010-12-28 6:50 ` Aneesh V
2010-12-28 7:49 ` Dirk Behme
2010-12-29 0:27 ` John Rigby
2010-12-29 0:26 ` John Rigby
2010-12-29 5:37 ` Aneesh V [this message]
2011-01-04 22:26 ` Scott Wood
2011-01-08 6:33 ` Aneesh V
2011-01-08 6:46 ` John Rigby
2011-01-08 8:33 ` Aneesh V
2011-01-08 17:43 ` John Rigby
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 7/8] mkimage: Add OMAP boot image support John Rigby
2011-01-04 13:43 ` Bedia, Vaibhav
2011-01-04 15:37 ` John Rigby
2010-12-28 0:47 ` [U-Boot] [RFC PATCH 8/8] OMAP3: Add ift target to top level Makefile John Rigby
2010-12-28 9:37 ` Dirk Behme
2010-12-28 6:17 ` [U-Boot] [RFC PATCH 0/8] Add nand_spl support for TI OMAP Beagle Aneesh V
2010-12-29 0:29 ` John Rigby
2010-12-28 19:49 ` Paulraj, Sandeep
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=4D1AC904.6020808@ti.com \
--to=aneesh@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