All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Neil Russell <caret@c-side.com>
Cc: Ruedi.Hofer@ascom.ch, linuxppc-embedded@lists.linuxppc.org,
	kernel@linux01.hasler.ascom.ch
Subject: Re: Limon & PowerQUICC II, Booting the kernel
Date: Tue, 26 Sep 2000 18:27:47 -0400	[thread overview]
Message-ID: <39D122E3.608630C5@mvista.com> (raw)
In-Reply-To: 20000926091205.A22470@lx.c-side.com


Neil Russell wrote:

> The downloaded kernel can be 4M-1K (0x3ffc00) in size, so I don't bother
> with compressing it.


Yes, please bother compressing it.  Making zImage is more than just
compressing the file.  The code in arch/ppc/mbxboot will (interactively)
create the command line, properly allocate the initial ram disk, and
most importantly creates the board information structure that is
required
by the kernel.  There is also hardware initialization expected by the
kernel that is often coordinated in the various functions found in
the arch/ppc/mbxboot files.  You can't simply boot vmlinux on an
embedded
system and expect it to work (unless your boot rom is doing exactly
the functions of arch/ppc/mbxboot).

The ELF header of the resulting zImage should be removed by just
using 'dd':
	dd if=zImage bs=64k skip=1 of=zImage.bin

Using objcopy or other generic programs on zImage will likely result
in a mess, because the file isn't really a valid ELF image.

> limon uses an enhanced version of the bootinfo structure (not the same as
> bd_info).

The kernel expects a board info that matches what it was configured to
use.  Every board is different.  You should modify
arch/ppc/mbxboot/misc.c
to know it was called by limon and properly convert or discover
information
necessary for the kernel version of the structure.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-09-26 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-26 12:49 Limon & PowerQUICC II, Booting the kernel Ruedi.Hofer
2000-09-26 16:12 ` Neil Russell
2000-09-26 22:27   ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-28  2:27 ZHANG,HAI-TAO (Non-A-China,ex1)
2000-09-25 15:24 Ruedi.Hofer
2000-09-03  1:39 ` Wang Chao Feng
2000-09-26 15:37 ` Dan Malek

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=39D122E3.608630C5@mvista.com \
    --to=dan@mvista.com \
    --cc=Ruedi.Hofer@ascom.ch \
    --cc=caret@c-side.com \
    --cc=kernel@linux01.hasler.ascom.ch \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.