From: Kevin A. Sapp <Kevin.Sapp@catapult.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] malloc error
Date: Fri, 16 Jan 2004 13:26:41 -0500 [thread overview]
Message-ID: <40082CE1.40905@catapult.com> (raw)
In-Reply-To: <20040116161455.5EFBFC10AF@atlas.denx.de>
Hello,
I have been porting das u-boot to run directly out of
RAM. So far so good, boots, serial works, ethernet works..
After I tftpboot a known good Linux kernel and try to
bootm it it fails while inflating the kernel in inflate_blocks_new
due to a malloc failure. I reserved 1MB of RAM for
malloc in the config file, but when malloc is called there
is not enough memory.
The board is an 8275 with 32MB of RAM. das u-boot is
downloaded with a BDI to 0.
Any ideas?
Thank you
Kevin
>
>
next prev parent reply other threads:[~2004-01-16 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 14:41 [U-Boot-Users] Board hangs during relocate_code sudhakar rajashekhara
2004-01-16 15:21 ` Wolfgang Denk
2004-01-16 15:50 ` Carsten Koester
2004-01-16 16:12 ` listmember at orkun.us
2004-01-16 16:14 ` Wolfgang Denk
2004-01-16 18:26 ` Kevin A. Sapp [this message]
2004-01-18 15:03 ` [U-Boot-Users] malloc error Wolfgang Denk
2004-01-18 17:12 ` Kevin A. Sapp
2004-01-18 17:27 ` Wolfgang Denk
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=40082CE1.40905@catapult.com \
--to=kevin.sapp@catapult.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