linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Pokki <kalle.pokki@iki.fi>
To: "David H. Lynch Jr" <dhlii@comcast.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Need help Understanding initial memory conditions.
Date: Wed, 19 Oct 2005 08:37:41 +0200	[thread overview]
Message-ID: <4355E9B5.30106@iki.fi> (raw)
In-Reply-To: <4355D6C1.4030004@comcast.net>

David H. Lynch Jr wrote:

> Alright I have RAM at physical 0x0 now.  I throw a copy of a 
> compressed linux image into RAM (anywhere special ?) load the assorted 
> registers with the appropriate values, fill the board info struct., 
> and just jump to the start of the image and pray that load text starts 
> coming out my serial port ?

Basically, but the exact thing to do depends which image you take. The 
build process results in a few different image files. I usually just 
take the vmlinux ELF file, and then my own scripts objcopy it to binary, 
compress, objcopy to an object file, and link the compressed image 
directly to the boot loader. The boot loader is then, of course, 
responsible of uncompressing the image to RAM to 0x00000000.

I think the kernel build can also create some "self-extracting" images, 
but I have never tried those. Maybe they don't even work anymore, as 
many (most?)  people just use the U-boot images.

  reply	other threads:[~2005-10-19  6:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  8:04 Need help Understanding initial memory conditions David H. Lynch Jr
2005-10-18  8:49 ` Kalle Pokki
2005-10-18 19:15   ` David H. Lynch Jr.
2005-10-18 20:14     ` Kalle Pokki
2005-10-19  5:16       ` David H. Lynch Jr
2005-10-19  6:37         ` Kalle Pokki [this message]
2005-10-19 10:24           ` Andrei Konovalov

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=4355E9B5.30106@iki.fi \
    --to=kalle.pokki@iki.fi \
    --cc=dhlii@comcast.net \
    --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;
as well as URLs for NNTP newsgroup(s).