From: Guan Xuetao <gxt-TG0Ac1+ktVePQbnJrJN+5g@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Michal Marek <mmarek-AlSwsSmVLrQ@public.gmane.org>,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org,
linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
microblaze-uclinux-rVRm/Wmeqae7NGdpmJTKYQ@public.gmane.org,
linux-kbuild-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Paul Mundt <lethal-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org>,
uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org,
sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Haavard Skinnemoen
<hskinnemoen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Hans-Christian Egtvedt
<egtvedt-BrfabpQBY5qlHtIdYg32fQ@public.gmane.org>
Subject: Re: [microblaze-linux] [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD
Date: Wed, 7 Mar 2012 14:52:43 +0800 [thread overview]
Message-ID: <1331103163.2048.33.camel@epip-laptop> (raw)
In-Reply-To: <1331080238-1524-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Tue, 2012-03-06 at 17:30 -0700, Stephen Warren wrote:
> This allows the user to use U-Boot's mkimage's -T kernel_noload option
> if their arch Kconfig allows it, and they desire.
>
> Signed-off-by: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
> ---
> The next patch enables this new CONFIG_ALLOW_ option for ARM. I assume
> that some other architectures will also be able to enable it, but I'm
> not familiar enough with any to know which.
>
> init/Kconfig | 15 +++++++++++++++
> scripts/Makefile.lib | 15 ++++++++++++---
> 2 files changed, 27 insertions(+), 3 deletions(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 6cfd71d..2035562 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -203,6 +203,21 @@ config KERNEL_LZO
>
> endchoice
>
> +config ALLOW_UIMAGE_KERNEL_NOLOAD
> + bool
> +
> +config UIMAGE_KERNEL_NOLOAD
> + bool "Use mkimage's -T kernel_noload instead of -T kernel"
> + depends on ALLOW_UIMAGE_KERNEL_NOLOAD
> + help
> + uImage files of type "kernel" embed an absolute load and entry point
> + address. If the uImage is loaded to a different address, then the
> + image must be copied the uImage file to the specified load address.
> + This copy is a waste of time if the uImage is in fact completely
> + relocatable. If your kernel and bootloader support it, you can build
> + a "kernel_noload" uImage rather than a "kernel" uImage, which
> + prevents any such copying. If unsure say N.
> +
> config DEFAULT_HOSTNAME
> string "Default hostname"
> default "(none)"
> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> index 7b0be18..d9c1c87 100644
> --- a/scripts/Makefile.lib
> +++ b/scripts/Makefile.lib
> @@ -314,9 +314,18 @@ MKIMAGE := $(srctree)/scripts/mkuboot.sh
> UIMAGE_ARCH = $(SRCARCH)
> UIMAGE_COMPRESSION = $(if $(2),$(2),none)
> UIMAGE_OPTS-y =
> -UIMAGE_TYPE = kernel
> -UIMAGE_LOADADDR=arch_must_set_this
> -UIMAGE_ENTRYADDR=$(UIMAGE_LOADADDR)
> +ifeq ($(CONFIG_UIMAGE_KERNEL_NOLOAD),y)
> + UIMAGE_TYPE = kernel_noload
> + # Unused by bootloader:
> + UIMAGE_LOADADDR=0
> + # Entry point relative to actual load address:
> + UIMAGE_ENTRYADDR=0
> +else
> + UIMAGE_TYPE = kernel
> + # Absolute addresses:
> + UIMAGE_LOADADDR=arch_must_set_this
> + UIMAGE_ENTRYADDR=$(UIMAGE_LOADADDR)
> +endif
> UIMAGE_NAME = 'Linux-$(KERNELRELEASE)'
> UIMAGE_IN = $<
> UIMAGE_OUT = $@
Hi, Stephen,
It seems that UIMAGE_ARCH and UIMAGE_LOADADDR can't be modified from
arch-Makefiles.
Regards,
Guan Xuetao
_______________________________________________
microblaze-linux mailing list
microblaze-linux-FR6EJeJVuqfA6Z3fQjNZrN9u6TNh0Fb7@public.gmane.org
https://lists.eait.uq.edu.au/mailman/listinfo/microblaze-linux
WARNING: multiple messages have this Message-ID (diff)
From: Guan Xuetao <gxt@mprc.pku.edu.cn>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Michal Marek <mmarek@suse.cz>,
Russell King <linux@arm.linux.org.uk>,
nico@fluxnic.net, Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Mike Frysinger <vapier@gentoo.org>,
Michal Simek <monstr@monstr.eu>, Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-kbuild@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,
sparclinux@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD
Date: Wed, 07 Mar 2012 14:52:43 +0800 [thread overview]
Message-ID: <1331103163.2048.33.camel@epip-laptop> (raw)
Message-ID: <20120307065243.iGL4emtq4eUyvJA00fEvsIOgjwo0970RXf3Z59FEuHY@z> (raw)
In-Reply-To: <1331080238-1524-2-git-send-email-swarren@wwwdotorg.org>
On Tue, 2012-03-06 at 17:30 -0700, Stephen Warren wrote:
> This allows the user to use U-Boot's mkimage's -T kernel_noload option
> if their arch Kconfig allows it, and they desire.
>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
> ---
> The next patch enables this new CONFIG_ALLOW_ option for ARM. I assume
> that some other architectures will also be able to enable it, but I'm
> not familiar enough with any to know which.
>
> init/Kconfig | 15 +++++++++++++++
> scripts/Makefile.lib | 15 ++++++++++++---
> 2 files changed, 27 insertions(+), 3 deletions(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 6cfd71d..2035562 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -203,6 +203,21 @@ config KERNEL_LZO
>
> endchoice
>
> +config ALLOW_UIMAGE_KERNEL_NOLOAD
> + bool
> +
> +config UIMAGE_KERNEL_NOLOAD
> + bool "Use mkimage's -T kernel_noload instead of -T kernel"
> + depends on ALLOW_UIMAGE_KERNEL_NOLOAD
> + help
> + uImage files of type "kernel" embed an absolute load and entry point
> + address. If the uImage is loaded to a different address, then the
> + image must be copied the uImage file to the specified load address.
> + This copy is a waste of time if the uImage is in fact completely
> + relocatable. If your kernel and bootloader support it, you can build
> + a "kernel_noload" uImage rather than a "kernel" uImage, which
> + prevents any such copying. If unsure say N.
> +
> config DEFAULT_HOSTNAME
> string "Default hostname"
> default "(none)"
> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> index 7b0be18..d9c1c87 100644
> --- a/scripts/Makefile.lib
> +++ b/scripts/Makefile.lib
> @@ -314,9 +314,18 @@ MKIMAGE := $(srctree)/scripts/mkuboot.sh
> UIMAGE_ARCH = $(SRCARCH)
> UIMAGE_COMPRESSION = $(if $(2),$(2),none)
> UIMAGE_OPTS-y =
> -UIMAGE_TYPE = kernel
> -UIMAGE_LOADADDR=arch_must_set_this
> -UIMAGE_ENTRYADDR=$(UIMAGE_LOADADDR)
> +ifeq ($(CONFIG_UIMAGE_KERNEL_NOLOAD),y)
> + UIMAGE_TYPE = kernel_noload
> + # Unused by bootloader:
> + UIMAGE_LOADADDR=0
> + # Entry point relative to actual load address:
> + UIMAGE_ENTRYADDR=0
> +else
> + UIMAGE_TYPE = kernel
> + # Absolute addresses:
> + UIMAGE_LOADADDR=arch_must_set_this
> + UIMAGE_ENTRYADDR=$(UIMAGE_LOADADDR)
> +endif
> UIMAGE_NAME = 'Linux-$(KERNELRELEASE)'
> UIMAGE_IN = $<
> UIMAGE_OUT = $@
Hi, Stephen,
It seems that UIMAGE_ARCH and UIMAGE_LOADADDR can't be modified from
arch-Makefiles.
Regards,
Guan Xuetao
next prev parent reply other threads:[~2012-03-07 6:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 0:30 [PATCH 1/3] Kbuild: centralize MKIMAGE and cmd_uimage definitions Stephen Warren
2012-03-07 0:30 ` Stephen Warren
2012-03-07 0:30 ` [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD Stephen Warren
2012-03-07 0:30 ` Stephen Warren
2012-03-07 0:52 ` Julian Calaby
2012-03-07 0:52 ` Julian Calaby
[not found] ` <1331080238-1524-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-03-07 6:52 ` Guan Xuetao [this message]
2012-03-07 6:52 ` Guan Xuetao
2012-03-07 18:10 ` Stephen Warren
2012-03-07 18:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 18:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 18:40 ` Stephen Warren
2012-03-07 18:36 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:02 ` Nicolas Pitre
2012-03-07 20:27 ` Stephen Warren
2012-03-07 21:03 ` Nicolas Pitre
2012-03-07 21:03 ` Nicolas Pitre
2012-03-07 21:30 ` Russell King - ARM Linux
2012-03-07 22:43 ` Nicolas Pitre
2012-03-07 21:28 ` Russell King - ARM Linux
2012-03-07 18:40 ` Stephen Warren
2012-03-07 18:50 ` Nicolas Pitre
2012-03-07 19:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:31 ` Nicolas Pitre
2012-03-07 19:31 ` Nicolas Pitre
2012-03-07 0:30 ` [PATCH 3/3] ARM: Allow the user to enable UIMAGE_KERNEL_NOLOAD Stephen Warren
2012-03-07 0:30 ` Stephen Warren
2012-03-07 3:56 ` [PATCH 1/3] Kbuild: centralize MKIMAGE and cmd_uimage definitions Mike Frysinger
2012-03-07 3:56 ` Mike Frysinger
2012-03-07 17:41 ` Stephen Warren
2012-03-07 17:41 ` Stephen Warren
2012-03-07 18:25 ` Mike Frysinger
2012-03-07 9:00 ` Hans-Christian Egtvedt
2012-03-07 9:00 ` Hans-Christian Egtvedt
2012-03-07 14:15 ` Josh Boyer
2012-03-07 18:29 ` Stephen Warren
2012-03-07 18:29 ` Stephen Warren
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=1331103163.2048.33.camel@epip-laptop \
--to=gxt-tg0ac1+ktvepqbnjrjn+5g@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=egtvedt-BrfabpQBY5qlHtIdYg32fQ@public.gmane.org \
--cc=hskinnemoen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=lethal-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kbuild-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=microblaze-uclinux-rVRm/Wmeqae7NGdpmJTKYQ@public.gmane.org \
--cc=mmarek-AlSwsSmVLrQ@public.gmane.org \
--cc=nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org \
--cc=sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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).