LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <srinivas.surabhi@wipro.com>
To: <david.jander@protonic.nl>, <linuxppc-embedded@ozlabs.org>
Subject: mkImage -e option for 4MB virtual entry point address of vmlinux
Date: Mon, 21 Feb 2005 15:18:12 +0530	[thread overview]
Message-ID: <EF9B29C78F41FA488927FCBC7750AF0E011DA684@hyd-mdp-msg.wipro.com> (raw)


In the last lines of the build which contains the below

ppc_82xx-ld -T ../ld.script -Ttext 0x00400000 -Bstatic -o zvmlinux
head.o

means that the entry address is 0x400000 ( 4MB) . Does it mean that the
while making mkImage for the kernel the -e option should be given
0x400000? And the load address option should also be the same for linux
kernel image or Is it ok if the load address is 0x0 address?



Thanks & Regards
Surabhi Srinivas

-----Original Message-----
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of David Jander
Sent: Monday, February 21, 2005 1:08 PM
To: linuxppc-embedded@ozlabs.org
Subject: Re: Freeing unused kernel memory: 56k init

On Sunday 20 February 2005 16:25, srinivas.surabhi@wipro.com wrote:
> When I tried to debug for the reason of  "Freeing unused kernel
memory:
> 56k init " hang problem  the following is the printk outputs...
>
> Entering kernel_read
>
> Entering elf_map
>
> map_addr was 0x30026000

Heh? Weired address. I'd expect something above 0xc0000000

> Failed due to bad address

No wonder....

> >From the above can anything be concluded ?
>
> One more doubt was, is it mandatory that the Virtual memory has to
> enabled while building the Mounta Vista linux kernel ? Why because
there
> was an option to enable the kernel base address and if it is enabled
it
> asks for what is the address for the Kernel Virtual base address? If I
> give 0x0 it works otherwise the Kernel itself is not at all booting.

Ok, don't say no more! Do not ever change that address unless you know
exactly=0D
what you are doing. It should be 0xc0000000 usually.
If the kernel doesn't boot, something else is wrong.
The linux kernel uses virtual memory, that's why it needs an MMU for
instance.=0D
That way, the memory the kernel uses and runs in is always mapped at
address=0D
0xc0000000.

> Till the statement "Freeing unused kernel memory: 56k init"  is coming
> only if and if the 0x0 was given for the kernel virtual base address.

That's actually pretty funny. I'd never thought about doing such an
experiment=0D
and expecting it to do something :-)

Greetings,

--=0D
David Jander
Protonic Holland.
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded



Confidentiality Notice=0D

The information contained in this electronic message and any attachments to=
 this message are intended
for the exclusive use of the addressee(s) and may contain confidential or=
 privileged information. If
you are not the intended recipient, please notify the sender at Wipro or=
 Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

                 reply	other threads:[~2005-02-21  9:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=EF9B29C78F41FA488927FCBC7750AF0E011DA684@hyd-mdp-msg.wipro.com \
    --to=srinivas.surabhi@wipro.com \
    --cc=david.jander@protonic.nl \
    --cc=linuxppc-embedded@ozlabs.org \
    /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