U-Boot: memory configuration

Hello

I was reading the U-Boot's README, section "Memory management". I don't
quite understand, so please help me out:
1) does this section embrace various platforms and describe generic behavior
of U-boot or PPC-specific?
2) it presents memory configuration, as I understand, for the case of
booting from flash. How will it look when u-boot is loaded in RAM by
preliminary boot code?

I specifically want to understand how memory is organized by U-Boot on ARM
platform, if there's difference.

Thanks in advance.

Best regards, Roman Mashak


.

Relevant Pages

  • Re: PCI bus operations and driver design
    ... is it possible for a write to memory mapped DPRAM to occasionally ... > the concern of individual device drivers. ... On some platforms you could ... >>scenarios when performing such operations over a PCI bus? ...
    (microsoft.public.development.device.drivers)
  • Re: [PATCH] asm-generic: add dma-mapping-linear.h
    ... It's fine if your DMA-able memory starts at physical address 0 and ends ... but this is no longer the case with embedded platforms. ... DMA capable. ... The device sets a mask of the address ranges it can ...
    (Linux-Kernel)
  • Re: copy_from_user/copy_to_user question
    ... >> Hmm, I've only worked with a few platforms (i386, ... >> memory is mapped its OK). ... So in the driver then ... You may need to wait till the data cache writes it ...
    (Linux-Kernel)
  • Re: malloc() -- Performance?
    ... It is advantageous to keep data in registers ... In any case modern platforms do the job for you so well that you ... > register during a loop may be loaded and written to memory each time ... doesn't help at all with porting code across platforms. ...
    (comp.lang.c)
  • Re: ASMM question
    ... how much memory will it try to allocate? ... If I run "show sga" on the instance it says total sga size is 6g. ... On these platforms the sga_target should = the sga_max. ...
    (comp.databases.oracle.server)