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@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH iproute2] Re: HTB accuracy for high speed |
