From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] alpr U-Boot image too big
Date: Tue, 9 Dec 2008 20:05:52 +0100 [thread overview]
Message-ID: <200812092005.52312.sr@denx.de> (raw)
In-Reply-To: <4CD35CD1F8085945B597F80EEC89421301B966E9@exc01.bk.prodrive.nl>
Hi Pieter,
On Tuesday 09 December 2008, Pieter Voorthuijsen wrote:
> I think I missed the previous mail during my holiday. I quickly checked the
> header file, here what can be undefined from the CONFIG_CMD_xx's:
>
> #define CONFIG_CMD_REGINFO
> #define CONFIG_CMD_NFS
> #define CONFIG_CMD_PCI
Are you really sure that you want to drop the PCI commands? IIRC then the ALPR
has some PCI devices and it might be handy to access them from within U-Boot
(for debugging etc).
> I also believe CMD_ELF is not needed for only booting a kernel, but not
> sure.
Yes, CMD_ELF is not needed for Linux kernel booting.
> I'm sure that disabling these will save enough kilobytes to make it fit....
I just checked and by disabling these features we fit into the 256k again:
#undef CONFIG_CMD_NFS
#undef CONFIG_CMD_REGINFO
#undef CONFIG_CMD_ELF
I'll submit a patch in a sec. Please send your ack if you think this is ok.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2008-12-09 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 12:47 [U-Boot] alpr U-Boot image too big Stefan Roese
2008-12-09 16:15 ` Stefan Roese
2008-12-09 17:50 ` Pieter Voorthuijsen
2008-12-09 19:05 ` Stefan Roese [this message]
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=200812092005.52312.sr@denx.de \
--to=sr@denx.de \
--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