From: Peter Tyser <ptyser@xes-inc.com>
To: linuxppc-dev@ozlabs.org
Cc: Peter Tyser <ptyser@xes-inc.com>, linux-kbuild@vger.kernel.org
Subject: [PATCH 0/3] powerpc: Add support for FIT uImages
Date: Wed, 18 Nov 2009 14:57:11 -0600 [thread overview]
Message-ID: <1258577834-26006-1-git-send-email-ptyser@xes-inc.com> (raw)
These patches add support for creating the "new" FIT uImage type
that U-Boot can use. Additional info about FIT images can be
found in the doc/uImage.FIT/ directory of the U-Boot source.
Here's a link to a howto which gives an overview of the format:
http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=doc/uImage.FIT/howto.txt;h=8065e9e1d8d4d65a9b5fe0fce08d3709183d0ee4;hb=HEAD
I've only added support for PowerPC, but the arm, avr32, blackfin,
and sh arches could use the same framework in theory. The change
is especially useful on PowerPC since it creates 1 FIT uImage that
combines the functionality of an "old" uImage format, a device
tree blob, and possibly a ramdisk.
Peter Tyser (3):
powerpc: Use scripts/mkuboot.sh instead of 'mkimage'
powerpc: Add support for creating FIT uImages
powerpc: Add support for ram filesystems in FIT uImages
arch/powerpc/Makefile | 4 +-
arch/powerpc/boot/.gitignore | 1 +
arch/powerpc/boot/Makefile | 8 ++-
arch/powerpc/boot/wrapper | 39 ++++++++++--
scripts/mkits.sh | 144 ++++++++++++++++++++++++++++++++++++++++++
5 files changed, 189 insertions(+), 7 deletions(-)
create mode 100755 scripts/mkits.sh
next reply other threads:[~2009-11-18 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 20:57 Peter Tyser [this message]
2009-11-18 20:57 ` [PATCH 1/3] powerpc: Use scripts/mkuboot.sh instead of 'mkimage' Peter Tyser
2009-11-18 20:57 ` [PATCH 2/3] powerpc: Add support for creating FIT uImages Peter Tyser
2009-11-18 20:57 ` [PATCH 3/3] powerpc: Add support for ram filesystems in " Peter Tyser
2009-11-18 21:51 ` [PATCH 0/3] powerpc: Add support for " Peter Tyser
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=1258577834-26006-1-git-send-email-ptyser@xes-inc.com \
--to=ptyser@xes-inc.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@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 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).