From: "H. Peter Anvin" <hpa@zytor.com>
To: ravikumar.chakaravarthy@amd.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Loading and executing kernel from a non-standard address usin g SY SLINUX
Date: Thu, 20 Mar 2003 15:07:18 -0800 [thread overview]
Message-ID: <3E7A49A6.5000908@zytor.com> (raw)
In-Reply-To: <99F2150714F93F448942F9A9F112634CA54B2D@txexmtae.amd.com>
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
next prev parent reply other threads:[~2003-03-20 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 22:56 Loading and executing kernel from a non-standard address usin g SY SLINUX ravikumar.chakaravarthy
2003-03-20 23:07 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 14:56 ravikumar.chakaravarthy
2003-03-07 15:46 ravikumar.chakaravarthy
2003-03-05 22:55 ravikumar.chakaravarthy
2003-03-04 18:47 ravikumar.chakaravarthy
2003-03-04 17:55 ravikumar.chakaravarthy
2003-03-04 18:12 ` Martin J. Bligh
2003-03-05 21:39 ` Kai Germaschewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E7A49A6.5000908@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravikumar.chakaravarthy@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.