linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: samble@xopnetworks.com
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Kernel boot
Date: Tue, 11 Feb 2003 00:36:28 +0100	[thread overview]
Message-ID: <20030210233633.562CAC6090@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 10 Feb 2003 16:44:53 CST." <200302101644.53246.samble@xopnetworks.com>


In message <200302101644.53246.samble@xopnetworks.com> you wrote:
>
> I am using ELDK-2.0 to create a bootable kernel image for PPC8xx. I have
> PPCBoot on my target and I want to download the kernel from the host to the
> target using TFTP boot. I have verified that I can transfer the image via
> TFTP boot. I am creating the initrd image using the following sequence of
> commands.

There is basicly zero relevance to Linux so this is off topic on this
list. You should ask this on the U-Boot-Users mailing list instead.

> 1. make config
> 2. make dep
> 3. make clean

OK so far.

> 4. make zImage.initrd

Wrong. Please see the README for instructions how to  build  a  Linux
image for use with U-Boot / PPCBoot.

> 5. Compress the "zvmlinux.initrd" executable using "gzip"

Twice wrong.

> 6. Execute mkimage command to prepare it for "ppcboot"

Completely bogus.

> responds. Can one of you please point to where I may be going wrong?

Please read the available documentation.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
No question is too silly to ask. Of course, some  questions  are  too
silly to to answer...  - L. Wall & R. L. Schwartz, _Programming Perl_

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

  reply	other threads:[~2003-02-10 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 22:44 Kernel boot Srini Amble
2003-02-10 23:36 ` Wolfgang Denk [this message]
2003-02-11  8:45 ` wolfgang.grandegger

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=20030210233633.562CAC6090@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=samble@xopnetworks.com \
    /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).