From: Kevin A. Sapp <Kevin.Sapp@catapult.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] malloc error
Date: Sun, 18 Jan 2004 12:12:14 -0500 [thread overview]
Message-ID: <400ABE6E.2090404@catapult.com> (raw)
In-Reply-To: <20040118150341.F3043C10AF@atlas.denx.de>
Wolfgang,
Thank you for the response.
My target will have 256M of RAM and I
can locate das u-boot anywhere in this range so
that it is not overwritten during the Linux boot process.
Would the top of RAM be a better choice then?
If das u-boot is not viable after Linux is started
that is fine, the system will re-download das u-boot
when required.
Thanks
Kevin
Wolfgang Denk wrote:
>In message <40082CE1.40905@catapult.com> you wrote:
>
>
>>I have been porting das u-boot to run directly out of
>>RAM. So far so good, boots, serial works, ethernet works..
>>
>>
>
>Running U-Boot out of RAM requires some understanding of the
>underlying principles.
>
>
>
>>The board is an 8275 with 32MB of RAM. das u-boot is
>>downloaded with a BDI to 0.
>>
>>
>
>This will never work. You cannot boot Linux that way, as the Linux
>kernel will overwrite U-Boot when you try to boot it.
>
>Best regards,
>
>Wolfgang Denk
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20040118/12faaca8/attachment.htm
next prev parent reply other threads:[~2004-01-18 17:12 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 ` [U-Boot-Users] malloc error Kevin A. Sapp
2004-01-18 15:03 ` Wolfgang Denk
2004-01-18 17:12 ` Kevin A. Sapp [this message]
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=400ABE6E.2090404@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