Messages in this thread | | | From | ravikumar.chakaravarthy@amd ... | Subject | RE: Loading and executing kernel from a non-standard address usin g SY SLINUX | Date | Fri, 21 Mar 2003 08:56:25 -0600 |
| |
Is there a way I can get away with this error? What changes would I have to make??
-Ravi
-----Original Message----- From: H. Peter Anvin [mailto:hpa@zytor.com] Sent: Thursday, March 20, 2003 5:07 PM To: Chakaravarthy, Ravikumar Cc: linux-kernel@vger.kernel.org Subject: Re: Loading and executing kernel from a non-standard address usin g SY SLINUX
ravikumar.chakaravarthy@amd.com wrote: > I tweaked the SYSLINUX boot loader and kernel to load and execute the kernel from 0x200000 (physical address). However when I try to load the kernel using the SYSLINUX bootloader to an address 0xdf000000(physical address) it doesn't work!! > I want to know if the following should work. > > 1. Should the syslinux be able to copy to the address DI=(0xdf000000). I think bcopy function in (SYSLINUX sources) does this.. Though the bcopy is done in the 32-bit mode, SOMETIMES it fails for this physical address). bcopy is called in runkernel.inc.
Yes.
> 2. Will I have any problem in the setup.S code in arch/i386/boot or head.S in arch/i386/boot/compressed because of this copy to 0xdf000000?? At times when it gets past step 1, it fails in malloc in arch/i386/boot/compressed/misc.c. The error it gives in "Memory Error"
Almost certainly.
-hpa
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |