From: Mike Frysinger <vapier.adi@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] uImage: Allow to specify MKIMAGE
Date: Sat, 20 Mar 2010 20:46:03 +0000 [thread overview]
Message-ID: <8bd0f97a1003201346xc927340r39f33b9a6b599792@mail.gmail.com> (raw)
In-Reply-To: <20100320184907.8036.82488.stgit@localhost.localdomain>
On Sat, Mar 20, 2010 at 14:49, Paulius Zaleckas wrote:
> --- a/arch/blackfin/boot/Makefile
> +++ b/arch/blackfin/boot/Makefile
> @@ -6,7 +6,7 @@
> # for more details.
> #
>
> -MKIMAGE := $(srctree)/scripts/mkuboot.sh
> +MKIMAGE := $(CONFIG_SHELL) $(srctree)/scripts/mkuboot.sh
>
> targets := vmImage vmImage.bin vmImage.bz2 vmImage.gz vmImage.lzma vmImage.xip
> extra-y += vmlinux.bin vmlinux.bin.gz vmlinux.bin.bz2 vmlinux.bin.lzma vmlinux.bin.xip
> @@ -16,7 +16,7 @@ UIMAGE_OPTS-$(CONFIG_RAMKERNEL) += -a $(CONFIG_BOOT_LOAD)
> UIMAGE_OPTS-$(CONFIG_ROMKERNEL) += -a $(CONFIG_ROM_BASE) -x
>
> quiet_cmd_uimage = UIMAGE $@
> - cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A $(ARCH) -O linux -T kernel \
> + cmd_uimage = $(MKIMAGE) -A $(ARCH) -O linux -T kernel \
> -C $(2) -n '$(MACHINE)-$(KERNELRELEASE)' \
> -e $(shell $(NM) vmlinux | awk '$$NF = "__start" {print $$1}') \
> $(UIMAGE_OPTS-y) -d $< $@
looks straightforward, and doesnt matter to me, so
Acked-by: Mike Frysinger <vapier@gentoo.org>
-mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Frysinger <vapier.adi@gmail.com>
To: Paulius Zaleckas <paulius.zaleckas@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
uclinux-dist-devel@blackfin.uclinux.org,
microblaze-uclinux@itee.uq.edu.au, linux-sh@vger.kernel.org,
hskinnemoen@atmel.com
Subject: Re: [PATCH] uImage: Allow to specify MKIMAGE
Date: Sat, 20 Mar 2010 16:46:03 -0400 [thread overview]
Message-ID: <8bd0f97a1003201346xc927340r39f33b9a6b599792@mail.gmail.com> (raw)
In-Reply-To: <20100320184907.8036.82488.stgit@localhost.localdomain>
On Sat, Mar 20, 2010 at 14:49, Paulius Zaleckas wrote:
> --- a/arch/blackfin/boot/Makefile
> +++ b/arch/blackfin/boot/Makefile
> @@ -6,7 +6,7 @@
> # for more details.
> #
>
> -MKIMAGE := $(srctree)/scripts/mkuboot.sh
> +MKIMAGE := $(CONFIG_SHELL) $(srctree)/scripts/mkuboot.sh
>
> targets := vmImage vmImage.bin vmImage.bz2 vmImage.gz vmImage.lzma vmImage.xip
> extra-y += vmlinux.bin vmlinux.bin.gz vmlinux.bin.bz2 vmlinux.bin.lzma vmlinux.bin.xip
> @@ -16,7 +16,7 @@ UIMAGE_OPTS-$(CONFIG_RAMKERNEL) += -a $(CONFIG_BOOT_LOAD)
> UIMAGE_OPTS-$(CONFIG_ROMKERNEL) += -a $(CONFIG_ROM_BASE) -x
>
> quiet_cmd_uimage = UIMAGE $@
> - cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A $(ARCH) -O linux -T kernel \
> + cmd_uimage = $(MKIMAGE) -A $(ARCH) -O linux -T kernel \
> -C $(2) -n '$(MACHINE)-$(KERNELRELEASE)' \
> -e $(shell $(NM) vmlinux | awk '$$NF == "__start" {print $$1}') \
> $(UIMAGE_OPTS-y) -d $< $@
looks straightforward, and doesnt matter to me, so
Acked-by: Mike Frysinger <vapier@gentoo.org>
-mike
WARNING: multiple messages have this Message-ID (diff)
From: vapier.adi@gmail.com (Mike Frysinger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] uImage: Allow to specify MKIMAGE
Date: Sat, 20 Mar 2010 16:46:03 -0400 [thread overview]
Message-ID: <8bd0f97a1003201346xc927340r39f33b9a6b599792@mail.gmail.com> (raw)
In-Reply-To: <20100320184907.8036.82488.stgit@localhost.localdomain>
On Sat, Mar 20, 2010 at 14:49, Paulius Zaleckas wrote:
> --- a/arch/blackfin/boot/Makefile
> +++ b/arch/blackfin/boot/Makefile
> @@ -6,7 +6,7 @@
> ?# for more details.
> ?#
>
> -MKIMAGE := $(srctree)/scripts/mkuboot.sh
> +MKIMAGE := $(CONFIG_SHELL) $(srctree)/scripts/mkuboot.sh
>
> ?targets := vmImage vmImage.bin vmImage.bz2 vmImage.gz vmImage.lzma vmImage.xip
> ?extra-y += vmlinux.bin vmlinux.bin.gz vmlinux.bin.bz2 vmlinux.bin.lzma vmlinux.bin.xip
> @@ -16,7 +16,7 @@ UIMAGE_OPTS-$(CONFIG_RAMKERNEL) += -a $(CONFIG_BOOT_LOAD)
> ?UIMAGE_OPTS-$(CONFIG_ROMKERNEL) += -a $(CONFIG_ROM_BASE) -x
>
> ?quiet_cmd_uimage = UIMAGE ?$@
> - ? ? ?cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A $(ARCH) -O linux -T kernel \
> + ? ? ?cmd_uimage = $(MKIMAGE) -A $(ARCH) -O linux -T kernel \
> ? ? ? ? ? ? ? ? ? ?-C $(2) -n '$(MACHINE)-$(KERNELRELEASE)' \
> ? ? ? ? ? ? ? ? ? ?-e $(shell $(NM) vmlinux | awk '$$NF == "__start" {print $$1}') \
> ? ? ? ? ? ? ? ? ? ?$(UIMAGE_OPTS-y) -d $< $@
looks straightforward, and doesnt matter to me, so
Acked-by: Mike Frysinger <vapier@gentoo.org>
-mike
next prev parent reply other threads:[~2010-03-20 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 18:49 [PATCH] uImage: Allow to specify MKIMAGE Paulius Zaleckas
2010-03-20 18:49 ` Paulius Zaleckas
2010-03-20 18:49 ` Paulius Zaleckas
2010-03-20 20:46 ` Mike Frysinger [this message]
2010-03-20 20:46 ` Mike Frysinger
2010-03-20 20:46 ` Mike Frysinger
2010-03-23 4:05 ` Paul Mundt
2010-03-23 4:05 ` Paul Mundt
2010-03-23 4:05 ` Paul Mundt
2010-03-23 7:22 ` Michal Simek
2010-03-23 7:22 ` Michal Simek
2010-03-23 7:22 ` Michal Simek
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=8bd0f97a1003201346xc927340r39f33b9a6b599792@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.