From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: tegra: add kexec support to defconfig
Date: Thu, 03 Jan 2013 14:45:02 -0700 [thread overview]
Message-ID: <50E5FBDE.90804@wwwdotorg.org> (raw)
In-Reply-To: <20130103212903.GA27749@avionic-0098.adnet.avionic-design.de>
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@nvidia•com>
>>>>
>>>> Signed-off-by: Stephen Warren <swarren@nvidia•com> ---
>>>> 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.
next prev parent reply other threads:[~2013-01-03 21:45 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
2013-01-03 16:50 ` Stephen Warren
2013-01-03 21:05 ` Thierry Reding
2013-01-03 21:18 ` Stephen Warren
2013-01-03 21:29 ` Thierry Reding
2013-01-03 21:45 ` Stephen Warren [this message]
2013-01-04 20:08 ` Thierry Reding
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=50E5FBDE.90804@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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