linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, john.linn@xilinx.com
Subject: Re: [PATCH v2] powerpc/bootwrapper: Add documentation of boot wrapper targets
Date: Mon, 30 Jun 2008 19:45:06 +0200	[thread overview]
Message-ID: <48691BA2.3050001@denx.de> (raw)
In-Reply-To: <20080628050407.6067.90225.stgit@trillian.secretlab.ca>

Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
> 
> There have been many questions on and off the mailing list about how
> exactly the bootwrapper is used for embedded targets.  Add some
> documentation and help text to try and clarify the system.
> 
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>

<snip>

> diff --git a/Documentation/powerpc/bootwrapper.txt b/Documentation/powerpc/bootwrapper.txt
> new file mode 100644
> index 0000000..a03d73c
> --- /dev/null
> +++ b/Documentation/powerpc/bootwrapper.txt
> @@ -0,0 +1,141 @@
> +The PowerPC boot wrapper
> +------------------------
> +Copyright (C) Secret Lab Technologies Ltd.
> +
> +PowerPC image targets compresses and wraps the kernel image (vmlinux) with
> +a boot wrapper to make it usable by the system firmware.  There is no
> +standard PowerPC firmware interface, so the boot wrapper is designed to
> +be adaptable for each kind of image that needs to be built.
> +
> +The boot wrapper can be found in the arch/powerpc/boot/ directory.  The
> +Makefile in that directory has targets for all the available image types.
> +The different image types are used to support all of the various firmware
> +interfaces found on PowerPC platforms.  OpenFirmware is the most commonly
> +used firmare type on general purpose PowerPC systems from Apple, IBM and

typo, s/firmare/firmware/

<snip>

> diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> index b7d4c4c..754c7eb 100644
> --- a/arch/powerpc/Makefile
> +++ b/arch/powerpc/Makefile
> @@ -169,12 +169,25 @@ bootwrapper_install %.dtb:
>  	$(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
>  
>  define archhelp
> -  @echo '* zImage          - Compressed kernel image (arch/$(ARCH)/boot/zImage.*)'
> +  @echo '* zImage          - Build default images selected by kernel config'
> +  @echo '  zImage.*        - Compressed kernel image (arch/$(ARCH)/boot/zImage.*)'
> +  @echo '  uImage          - U-Book native image format'

typo, s/U-Book/U-Boot/

> +  @echo '  cuImage.<dt>    - Backwards compatible U-Boot image for older'
> +  @echo '                    versions which do not support device trees'
> +  @echo '  dtbImage.<dt>   - zImage with an embedded device tree blob'
> +  @echo '  simpleImage.<dt> - Firmware independant image.'

typo, s/independant/independent/

Cheers,
Anatolij

  parent reply	other threads:[~2008-06-30 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-28  5:04 [PATCH v2] powerpc/bootwrapper: Add documentation of boot wrapper targets Grant Likely
2008-06-30  5:03 ` Paul Mackerras
2008-06-30 16:15   ` Grant Likely
2008-06-30 17:45 ` Anatolij Gustschin [this message]
2008-06-30 18:25   ` Grant Likely

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=48691BA2.3050001@denx.de \
    --to=agust@denx.de \
    --cc=grant.likely@secretlab.ca \
    --cc=john.linn@xilinx.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).