From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mtd: nand: oob data structures taking up a lot of space
Date: Fri, 13 Dec 2013 21:11:30 -0800 [thread overview]
Message-ID: <52ABE882.2010805@caviumnetworks.com> (raw)
Hi all,
I am working on trying to shrink down a bootloader for one of our chips
where the bootloader must fit in around 448K of memory and things are
fairly tight. I found that the oob data structures for 8, 16, 64 and 128
bytes were taking up a fair amount of space. I had to increase the
eccpos size to 640 to match the Linux kernel since the existing size was
too small for some of the NAND devices we are working with. This caused
each oob data structure to consume around 2.5K in the binary. By
initializing the layout data structures at runtime I was able to
eliminate most of the space taken since now the linker can place these
in BSS.
-Aaron
--
Aaron Williams
Software Engineer
Cavium, Inc.
(408) 943-7198 (510) 789-8988 (cell)
next reply other threads:[~2013-12-14 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 5:11 Aaron Williams [this message]
2013-12-18 4:02 ` [U-Boot] mtd: nand: oob data structures taking up a lot of space Scott Wood
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=52ABE882.2010805@caviumnetworks.com \
--to=aaron.williams@caviumnetworks.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