linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lou Rickard <lou_rickard@yahoo.com>
To: linuxppc-embedded@lists.linuxppc.org
Cc: dan@embeddededge.com
Subject: Re: coffboot?
Date: Fri, 19 Mar 2004 09:38:59 -0800 (PST)	[thread overview]
Message-ID: <20040319173859.61444.qmail@web21113.mail.yahoo.com> (raw)
In-Reply-To: <405B09D7.2010307@embeddededge.com>


Yeah, the Bright Star Engineering IP-Engine.

When I build the kernel from the bse development kit,
which has the 2.2 kernel, I see that a zImage file
(well, zImage is a sym. link to another file called
zvmlinux) gets built in the boot directory, and so
does zImage.gz in the coffboot directory.

The version in the coffboot directory works (when
built into the ramdisk image) works, the other one
(using the real file, not the symbolic link) doesn't.

When I build the kernel from my 2.4 directory, I end
up with a zImage.gz in the boot/images directory, but
it doesn't work.

I'm guessing there's something I've got to do to
convert the zImage.gz in my 2.4 boot/images directory
to coffboot format, but I don't know what that is, and
can't see how they do it in the bse dev kit.

~lr

--- Dan Malek <dan@embeddededge.com> wrote:
> You mean the Bright Star Engineering IP-Engine?  Or
> is
> this something else with the same name?


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

  reply	other threads:[~2004-03-19 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  2:07 coffboot? Lou Rickard
2004-03-19 14:55 ` coffboot? Dan Malek
2004-03-19 17:38   ` Lou Rickard [this message]
2004-03-19 18:47     ` coffboot? Dan Malek
2004-03-23 21:27       ` coffboot? Lou Rickard

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=20040319173859.61444.qmail@web21113.mail.yahoo.com \
    --to=lou_rickard@yahoo.com \
    --cc=dan@embeddededge.com \
    --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).