linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Kent Borg <kentborg@borg.org>
Cc: Dan Malek <dan@embeddededge.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: boot/simple in ROM?
Date: Thu, 24 Apr 2003 10:49:21 -0700	[thread overview]
Message-ID: <3EA823A1.7030905@mvista.com> (raw)
In-Reply-To: <20030424133222.B8490@borg.org>


Kent Borg wrote:

>On Thu, Apr 24, 2003 at 01:13:35PM -0400, Dan Malek wrote:
>
>
>>The other really nice thing about these bootloaders, compressed
>>kernels, and attached initrd, is you can boot the identical image
>>from all "devices."  For example, during development you can tftp
>>load the image, get everything working, then place the exact same
>>bits into a flash rom.  Simply jump to the first location of the
>>image and it will boot from flash.
>>
>>
>
>Yes, but disappointingly the ppc/boot/simple I am using (from 2.4
>devel) won't run from ROM.  Is there a better boot loader I should be
>using?
>
>
You're a little sparse on info here but try lopping off the first 64KB
of your zImage (or jump 0x10000 into the zImage that you have).

Mark


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

  reply	other threads:[~2003-04-24 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 16:33 boot/simple in ROM? Kent Borg
2003-04-24 17:13 ` Dan Malek
2003-04-24 17:32   ` Kent Borg
2003-04-24 17:49     ` Mark A. Greer [this message]
2003-04-24 18:41       ` Dan Malek
2003-04-24 18:29   ` emanuel stiebler
     [not found] <00032EDD.C22236@borg.org>
2003-04-24 17:44 ` Jerry Van Baren
2003-04-24 18:02   ` Mark A. Greer
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24 18:06 Kerl, John
2003-04-24 19:15 ` Kent Borg
2003-04-25 12:53 Wells, Charles
2003-04-25 14:48 ` 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=3EA823A1.7030905@mvista.com \
    --to=mgreer@mvista.com \
    --cc=dan@embeddededge.com \
    --cc=kentborg@borg.org \
    --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 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).