From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin A. Sapp <Kevin.Sapp@catapult.com>
Date: Sun, 18 Jan 2004 12:12:14 -0500
Subject: [U-Boot-Users] malloc error
In-Reply-To: <20040118150341.F3043C10AF@atlas.denx.de>
References: <20040118150341.F3043C10AF@atlas.denx.de>
Message-ID: <400ABE6E.2090404@catapult.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.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