On 9 Mar 2008 at 15:42, Wolfgang Denk wrote: > In message <[EMAIL PROTECTED]> you wrote: > > > The only thing missing for this is a working CONFIG_MONITOR_IS_IN_RAM > > as far as I can see. > > Actually this is not missing. All you need to do is to create a > configuration which (1) has a modfied TEXT_BASE and (2) skips the > memory initialization. But see > http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStartedInRAM
I know this is possible in theory. However, in my case (MCF5329/MCF537x) this stopped working with U-Boot 1.3.x, and I did not yet figure out what goes wrong. I just wanted to vote for not dropping this feature altogether, which I feared might happen as it is normally very much discouraged to use it. Regards, Wolfgang ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
