From: Thierry Reding <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: add kexec support to defconfig
Date: Fri, 4 Jan 2013 21:08:20 +0100 [thread overview]
Message-ID: <20130104200820.GC4577@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <50E5FBDE.90804-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
On Thu, Jan 03, 2013 at 02:45:02PM -0700, Stephen Warren wrote:
> On 01/03/2013 02:29 PM, Thierry Reding wrote:
> > On Thu, Jan 03, 2013 at 02:18:27PM -0700, Stephen Warren wrote:
> >> On 01/03/2013 02:05 PM, Thierry Reding wrote:
> >>> On Wed, Jan 02, 2013 at 02:12:21PM -0700, Stephen Warren
> >>> wrote:
> >>>> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> >>>>
> >>>> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> ---
> >>>> arch/arm/configs/tegra_defconfig | 1 + 1 file changed, 1
> >>>> insertion(+)
> >>>>
> >>>> diff --git a/arch/arm/configs/tegra_defconfig
> >>>> b/arch/arm/configs/tegra_defconfig index 742dc41..e621603
> >>>> 100644 --- a/arch/arm/configs/tegra_defconfig +++
> >>>> b/arch/arm/configs/tegra_defconfig @@ -34,6 +34,7 @@
> >>>> CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_ZBOOT_ROM_TEXT=0x0
> >>>> CONFIG_ZBOOT_ROM_BSS=0x0 +CONFIG_KEXEC=y CONFIG_CPU_FREQ=y
> >>>> CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y CONFIG_CPU_IDLE=y
> >>>
> >>> Interesting. What do you plan to use this for? kdump?
> >>
> >> I plan to burn a kernel (and a small stub, and a DTB) into flash
> >> instead of U-Boot, and hence not have to rely on any bootloader.
> >
> > Why does that require kexec support?
>
> Because I'd be using that kernel plus an initrd to download the "real"
> kernel over e.g. TFTP and kexec it.
Right, that makes sense. Thanks for explaining.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-04 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 21:12 [PATCH] ARM: tegra: add kexec support to defconfig Stephen Warren
[not found] ` <1357161141-26430-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-03 16:50 ` Stephen Warren
2013-01-03 21:05 ` Thierry Reding
[not found] ` <20130103210541.GB4412-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2013-01-03 21:18 ` Stephen Warren
[not found] ` <50E5F5A3.1060507-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-03 21:29 ` Thierry Reding
[not found] ` <20130103212903.GA27749-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2013-01-03 21:45 ` Stephen Warren
[not found] ` <50E5FBDE.90804-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-04 20:08 ` Thierry Reding [this message]
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=20130104200820.GC4577@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding-rm9k5ik7kjkj5m59nbduvrnah6klmebb@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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