From: Andriy Korud <a.korud@vector.com.pl>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 440GP "Ebony" boot problems
Date: Fri, 26 Nov 2004 10:13:31 +0100 [thread overview]
Message-ID: <1101460411.6134.2.camel@localhost> (raw)
In-Reply-To: <20041125185233.GA13325@gate.ebshome.net>
I also thought similar, but:
- make bzImage within stock 2.6.9 gives me zImage.elf
- when trying to boot Ebony with it I have:
Booting from [EMAC0] Ethernet 0 ...
Sending bootp request ...
Loading file "zImage.elf" ...
Sending tftp boot request ...
Not a valid boot image file
And I'm completely lost with this :-)
regards,
--
Andriy Korud
On Thu, 2004-11-25 at 10:52 -0800, Eugene Surovegin wrote:
> On Thu, Nov 25, 2004 at 05:18:49PM +0100, Andriy Korud wrote:
> > I'm trying to boot original 440GP "Ebony" board wiath original IBM ROM
> > Monitor:
> > ...
> > 440GP 1.18 ROM Monitor (02/11/02)
> > ...
> >
> > However I've discovered that it requires special image in KDI (Kernel
> > Downloadable Image) format. And it seems that the only way to make such
> > image is to use 'mkimage' utility from LynuxWorks which is not widely
> > available :-)
> > Can anybody help me with this?
>
> Huh? I'm away from my Ebony right now, so I cannot check which
> OpenBIOS version it has but I never heard about KDI.
>
> Image generated by the `make bzImage` in 2.4 or 2.6 official
> kernel should be bootable on Ebony with original IBM firmware.
>
> Why do you think IBM firmware requires LynuxWorks special image? This
> sounds like a nonsense, frankly.
>
> --
> Eugene
next prev parent reply other threads:[~2004-11-26 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 16:18 440GP "Ebony" boot problems Andriy Korud
2004-11-25 18:52 ` Eugene Surovegin
2004-11-26 9:13 ` Andriy Korud [this message]
2004-11-26 8:30 ` Eugene Surovegin
2004-11-26 10:28 ` Andriy Korud
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=1101460411.6134.2.camel@localhost \
--to=a.korud@vector.com.pl \
--cc=ebs@ebshome.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 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.