linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: C.Gillan@ecit.qub.ac.uk
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PPCBoot question
Date: Fri, 25 Jun 2004 14:57:01 +0200	[thread overview]
Message-ID: <20040625125706.5F625C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 25 Jun 2004 12:13:02 BST." <34753.143.117.36.139.1088161982.squirrel@143.117.36.139>


In message <34753.143.117.36.139.1088161982.squirrel@143.117.36.139> you wrote:
>
> I would like to to be able to build only one binary file
> to be used for download to the target, rather than have to
> download the kernel and filesystem separately. But, I'm not sure if
> this is possible and if it is, how to set up the bootm command
> to work with this. Perhaps, I've missed something in the documentation.

Yes, you missed the section "More About U-Boot Image  Types"  in  the
README  which  explains what "Multi-File Images" are and how they can
be used to do exactly what you are looking for, and you  also  missed
to    read    the    FAQ    section    in    the   DULG,   especially
http://www.denx.de/twiki/bin/view/DULG/CombiningKernelAndRamdisk

> As I understand it, the mkimage utility that comes with the PPCBoot/Das
> U-Boot bootloader software can build a combined image containing both
> the kernel and the file system - following is from the PPCBoot documentation:
>
>  -> tools/mkimage -n '2.2.13 for initrd on TQM850L' \
>         > -A ppc -O linux -T kernel -C gzip -a 00000000 -e 0000000C \
>         > -d /opt/mpc8xx/src/linux-2.2.13/arch/ppc/coffboot/vmlinux.gz \
>         > examples/image-2.2.13-initrd

Well, "-T kernel" requests for a "kernel type"  image.  If  you  want
something  else, use a different option (like -T multi" for multifile
images. See mkimage's useage message.

> My confusion arises from the fact that I don't see a way of
> specifying the address to which the file system will be downloaded,

You don;t have to care. U-Boot will do this automagically.

> As I understand it, I need to specify that address as the second
> argument on the bootm command, e.g.
>
>     bootm <kernel-address> <file-system-address>

This is just for separate images. With a multifile  image,  ther  eis
only one image and thus only one address argument for 'bootm'.

> I'd be grateful for any help received.

Chances for help would be better if you didn't post to  mailing  list
where  your  question  is off topic - this has actually nothing to do
with  linuxppc-embedded;  you  should  have  posted  to  u-boot-users
instead.

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
Time is a drug. Too much of it kills you.
                                      - Terry Pratchett, _Small Gods_

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

      reply	other threads:[~2004-06-25 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 11:13 PPCBoot question C.Gillan
2004-06-25 12:57 ` Wolfgang Denk [this message]

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=20040625125706.5F625C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=C.Gillan@ecit.qub.ac.uk \
    --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).