public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 8/8] OMAP3: Add ift target to top level Makefile
Date: Tue, 28 Dec 2010 10:37:47 +0100	[thread overview]
Message-ID: <4D19AFEB.3000104@googlemail.com> (raw)
In-Reply-To: <1293497228-15911-9-git-send-email-john.rigby@linaro.org>

On 28.12.2010 01:47, John Rigby wrote:
> Signed-off-by: John Rigby<john.rigby@linaro.org>
> ---
>   Makefile |    9 +++++++++
>   1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 9055028..baf11b3 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -289,8 +289,13 @@ LDPPFLAGS += \
>
>   ifeq ($(CONFIG_NAND_U_BOOT),y)
>   NAND_SPL = nand_spl
> +ifeq ($(CONFIG_OMAP3430),y)
> +U_BOOT_SPL_IFT=u-boot-spl.ift
> +ALL+=$(U_BOOT_SPL_IFT)
> +else
>   U_BOOT_NAND = $(obj)u-boot-nand.bin
>   endif
> +endif
>
>   ifeq ($(CONFIG_ONENAND_U_BOOT),y)
>   ONENAND_IPL = onenand_ipl
> @@ -407,6 +412,10 @@ $(NAND_SPL):	$(TIMESTAMP_FILE) $(VERSION_FILE) depend
>   $(U_BOOT_NAND):	$(NAND_SPL) $(obj)u-boot.bin
>   		cat $(obj)nand_spl/u-boot-spl-16k.bin $(obj)u-boot.bin>  $(obj)u-boot-nand.bin
>
> +$(U_BOOT_SPL_IFT):	$(NAND_SPL) $(obj)u-boot.bin
> +		$(obj)tools/mkimage -T omapimage \
> +		-a $(CONFIG_SYS_NAND_SPL_TEXT_BASE) -d $(obj)nand_spl/u-boot-spl.bin $@
> +
>   $(ONENAND_IPL):	$(TIMESTAMP_FILE) $(VERSION_FILE) $(obj)include/autoconf.mk
>   		$(MAKE) -C onenand_ipl/board/$(BOARDDIR) all

While I just saw

http://lists.denx.de/pipermail/u-boot/2010-December/084347.html

what's about adding u-boot-spl.ift to .gitignore, too?

Thanks

Dirk

  reply	other threads:[~2010-12-28  9:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28  0:47 [U-Boot] [RFC PATCH 0/8] Add nand_spl support for TI OMAP Beagle John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 1/8] NAND: nand_spl/nand_boot.c: add 16-bit and readid support John Rigby
2011-01-04 22:08   ` Scott Wood
2011-01-04 22:19     ` Scott Wood
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 2/8] armv7: add nand_spl support John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 3/8] OMAP3: and " John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 4/8] OMAP3: add dram timing constants from x-loader John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 5/8] NAND: omap_gpmc.c: add nand_spl support John Rigby
2011-01-04 22:24   ` Scott Wood
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 6/8] omap3_beagle: " John Rigby
2010-12-28  6:50   ` Aneesh V
2010-12-28  7:49     ` Dirk Behme
2010-12-29  0:27       ` John Rigby
2010-12-29  0:26     ` John Rigby
2010-12-29  5:37       ` Aneesh V
2011-01-04 22:26         ` Scott Wood
2011-01-08  6:33   ` Aneesh V
2011-01-08  6:46     ` John Rigby
2011-01-08  8:33       ` Aneesh V
2011-01-08 17:43         ` John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 7/8] mkimage: Add OMAP boot image support John Rigby
2011-01-04 13:43   ` Bedia, Vaibhav
2011-01-04 15:37     ` John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 8/8] OMAP3: Add ift target to top level Makefile John Rigby
2010-12-28  9:37   ` Dirk Behme [this message]
2010-12-28  6:17 ` [U-Boot] [RFC PATCH 0/8] Add nand_spl support for TI OMAP Beagle Aneesh V
2010-12-29  0:29   ` John Rigby
2010-12-28 19:49 ` Paulraj, Sandeep

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=4D19AFEB.3000104@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /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