Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Smucker <bsmucker@anabaptists.org>
To: kexec@lists.infradead.org
Subject: Re: Kexec for ARM: Is it expected to load old kernels?
Date: Mon, 12 Apr 2010 07:52:12 -0700	[thread overview]
Message-ID: <4BC3339C.9040903@anabaptists.org> (raw)
In-Reply-To: <n2id1b08f941004120500o43859311x8331038ceb84d1b7@mail.gmail.com>

Hi

So it appears I cannot load pre-2.6.24 kernels ARM kernels.  I have some 
further questions.

Is this an ARM-only thing?

If I want to load an arbitrary kernel, am I out of luck?

I thought theoretically kexec was able to execute arbitrary elf 
binaries, non-kernals, etc.  Is this true, or only my own misconception?

Or is it true in general, but not for ARM?

If it is not true for ARM, can I fix it?

I would like kexec to be able to boot old,old kernels, of the 2.4.16 
vintage.

Can you help answer these questions?

Thanks,

Brian



Andrea Adami wrote:
> Brian,
>
> I suppose you need the ATAG changes introduced in 2.6.24 in order to
> boot an arm kernel from kexec.
> There are around patches for 2.6.22 and 2.6.23
> (http://docs.openmoko.org/trac/ticket/930).
>
> See amongst others:
>
> [ARM] 4599/1: Preserve ATAG list for use with kexec (2.6.23)
> [ARM] 4836/1: Make ATAGS_PROC depend on KEXEC
>
>
> Regards
>
> Andrea
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>   


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2010-04-12 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10  0:44 Kexec for ARM: Is it expected to load old kernels? Brian Smucker
2010-04-12 12:00 ` Andrea Adami
2010-04-12 14:52   ` Brian Smucker [this message]
2010-04-14 17:01     ` Brian Smucker
2010-04-22 13:35       ` Eric W. Biederman
2010-04-22 13:36       ` Eric W. Biederman

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=4BC3339C.9040903@anabaptists.org \
    --to=bsmucker@anabaptists.org \
    --cc=kexec@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox