hi roman,
on which perticular board u r working on?
have you check the config.mk file in board/{board} specific folder.
in this file you have to define TEXT_BASE which is the address to load the uboot.
as per my understanding first stage of boot loader will load 2nd stage to this address.
if u will check the config.mk file u will get some idea.
correct me if i am wrong.
thanks,
mitul modi
on which perticular board u r working on?
have you check the config.mk file in board/{board} specific folder.
in this file you have to define TEXT_BASE which is the address to load the uboot.
as per my understanding first stage of boot loader will load 2nd stage to this address.
if u will check the config.mk file u will get some idea.
correct me if i am wrong.
thanks,
mitul modi
On Mon, Oct 6, 2008 at 6:05 PM, Roman Mashak <romez777@xxxxxxxxx> wrote:
Hello
I'm in for porting bootloader U-Boot and Linux on to ARM-based
platform. Now I've reached the point of defining a 'memory map' -- as
I understand this is done along with start address of Linux kernel,
i.e. what's in $(LINUX)/arch/arm/mach-<board>/Makefile.boot (speaking
of 2.6.x kernels).
What I don't quite understand is how are the images of bootloader
(U-Boot in my case), kernel, initrd (if any) laid out in memory, in
what sequences? Does U-Boot copy itself to upper addresses, followed
by kernel? As I know the Linux kernel expects parameteres to be
received on a specific address in ROM from a bootloader, for ARM
platforms these parameters are allocated in ATAG structures -- so how
is this address defined, according to chip's datasheet or somehow
else?
If someone could provide clear example explaining my question - I'd
appreciate a lot.
Thanks in advance.
--
Roman Mashak
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
