From: ravikumar.chakaravarthy@amd.com
To: mbligh@aracnet.com, linux-kernel@vger.kernel.org
Subject: RE: Loading and executing kernel from a non-standard address usin g SY SLINUX
Date: Tue, 4 Mar 2003 11:55:49 -0600 [thread overview]
Message-ID: <99F2150714F93F448942F9A9F112634CA54B08@txexmtae.amd.com> (raw)
Yes the kernel is uncompressed to the right location (0x200000), in my case. When I try to uncompress it to a non standard address (other than 0x100000), the address mapping is affected. Thats why I tried to change the PAGE_OFFSET value to 0xc0100000, which should be the right value corresponding to (0x200000).
So the problem now is that, when a function is invoked it is unable to fetch the right physical address, since my address mapping (System.map) does not change when I change the value of PAGE_OFFSET and recompile the kernel.
-Ravi
-----Original Message-----
From: Martin J. Bligh [mailto:mbligh@aracnet.com]
Sent: Tuesday, March 04, 2003 11:35 AM
To: Chakaravarthy, Ravikumar; linux-kernel@vger.kernel.org
Subject: Re: Loading and executing kernel from a non-standard address using SY SLINUX
> I am trying to load and boot the kernel from a non-standard address
> (0x200000). I am using the SYSLINUX boot loader, which loads the
> kernel at that address. I have also made changes to the kernel to
> setup code and startup_32() function to effect the same. When I boot
> the system It says
>
> Loading.......... Ready
> Uncompressing Linux... OK Booting the kernel
>
> and then hangs.
>
> I guess the reason being the System.map entries are still using the
> PAGE_OFFSET = 0xc0000000, as opposed to 0xc0100000.
> I have the following questions??
>
> 1. How do i change the System.map to get the right PAGE_OFFSET.
> 2. Will it work if I load and boot the kernel from a different address
> like (0xdf000000)??
>
> 3. Am I in the right track or missing something.
The kernel should decompress itself to the right space anyway ... check
arch/i386/boot/compressed/head.S ... should be minimal changes needed,
if any.
M.
-
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/
next reply other threads:[~2003-03-04 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 17:55 ravikumar.chakaravarthy [this message]
2003-03-04 18:12 ` Martin J. Bligh
2003-03-05 21:39 ` Kai Germaschewski
2003-03-04 18:47 ravikumar.chakaravarthy
2003-03-05 22:55 ravikumar.chakaravarthy
2003-03-07 15:46 ravikumar.chakaravarthy
2003-03-20 22:56 ravikumar.chakaravarthy
2003-03-20 23:07 ` H. Peter Anvin
2003-03-21 14:56 ravikumar.chakaravarthy
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=99F2150714F93F448942F9A9F112634CA54B08@txexmtae.amd.com \
--to=ravikumar.chakaravarthy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®