ok fine. But if kernel is loaded at 0x100000 and then deompresstion routine [head.S] decompresses the kernel at 0x100000 only, there is a possibility of overwriting the decompression routine's code by that of the decompressed kernel, as both are happening at the same place...so what about that ? Thanks. Sumit Sharma. On Wed, 22 Sep 2004 manish regmi wrote : >> Hi Manish, >>Thanks for making the things more clear. Now I got the point that in case of >>bzImage kernel is loaded at 0x1000 only, but as soon as you have loaded 64k of it, >>it will be moved to high mem [i.e. 0x100000]... tell me if I am wrong. So bzImage is >>never placed at physical location 0x1000. It means that now uncompression >>routines are loaded at 0x100000 [instead of 0x10000 with zImage] and then head.S >>and misc.c [which have been moved to 0x100000] will then uncompress the kernel >>at 0x100000 again ?? Please clear these points also... >> >>TIA. >>Sumit Sharma. >> > >Yes, >In bzImage, the image is loaded at 100000 using (int 15). >Then, the kernel jumps at 100000 using jmpi > >see setup.S line 803 > >Now, the code executed there is decompression routine. i.e. compressed/head.S > >There are codes to decompress the bzImage to 100000. > >regards manish > >_________________________________________________________________ >Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail >
