From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] arm: mmc: omap: spl size reduction by removing write/erase ops
Date: Thu, 02 Feb 2012 22:18:04 +0530 [thread overview]
Message-ID: <4F2ABE44.6090303@ti.com> (raw)
In-Reply-To: <CA+M6bX=Ev4aKm-1Xecnf8Z2peybS36USWqYqd-+9Nz8k36kx6w@mail.gmail.com>
Tom,
On Thursday 02 February 2012 10:02 PM, Tom Rini wrote:
> On Thu, Feb 2, 2012 at 6:04 AM, Balaji T K<balajitk@ti.com> wrote:
>> spl for OMAP4 does not use mmc read/write.
>> Add CONFIG_MMC_NO_ERASE, CONFIG_MMC_NO_WRITE to platforms where mmc
>> write/erase operation is not needed in spl.
>> Use these CONFIGS to remove write/erase code in mmc.c and omap_hsmmc.c
>> This reduces the spl size by ~1128 Bytes
>
> Are you running into a size limitation again? If not, I think we want
We are always on the border. Minor fluctuations are affecting us. And
our EMU boards(secure devices) are permanently broken due to this. I am
not sure if this one helps EMU devices though.
> to wait until we sort out how SPL includes/excludes stuff moving
> forward as this shows there's probably a lot of other unused code
> being pulled in.
>
We use -ffunction-sections -fdata-sections and --gc-sections while
building SPL. So, un-necessary stuff will not be included unless the
function pointers are set in some structures and not used. I think that
is what is happening in this case. Other than that I am not expecting
much scope for improvement.
One key experiment I want to do is Thumb mode build. I have some old
patches that I may cleanup and post sometime soon. But Thumb mode had
some tool-chain related issues last time I tried.
br,
Aneesh
next prev parent reply other threads:[~2012-02-02 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 13:04 [U-Boot] [PATCH 1/1] arm: mmc: omap: spl size reduction by removing write/erase ops Balaji T K
2012-02-02 16:32 ` Tom Rini
2012-02-02 16:48 ` Aneesh V [this message]
2012-02-02 17:13 ` 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=4F2ABE44.6090303@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