This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re: load address


YH wrote:
Hello,

I am going to run ARM with kernel 2.6, 32M DRAM and 16M Flash (Intel J3). Could you please help me the following questions:

Redboot> load -v -r -b 0xA00000 ramdisk.gz
Redboot> load -v -r -b 0x80000 zImage
Redboot> exec -r 0xA00000 -c "console=ttyAM root=/dev/ram"

1. I guess the address is the DRAM entry address. If the ramdisk.gz = 4M and the decompressed ramdisk = 12M, and zImage = 800K, I guess that the ramdisk will be allocated in DRAM between 0xA00000 - 0x1600000 and the zImage will be allocated in DRAM between 0x80000 - 0x148000. I guess those address sections of ramdisk and zImage are occupied during operation time, is it correct?

2. Can the DRAM loading addresses be selected anywhere, or it can only be selected in particular segments?

3. Do we need to allocate the memory (stack and heaps), or the kernel will use the rest of the available DRAM?


You should ask these questions of the ARM Linux folks.


--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]