All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Impending Kexec interface change
Date: Wed, 21 Feb 2007 00:39:53 +0000	[thread overview]
Message-ID: <1172018393.5884.122.camel@localhost.localdomain> (raw)
In-Reply-To: <432beae0702201436v78aa4959q59cdad54da6a2627@mail.gmail.com>

On Tue, 2007-02-20 at 14:36 -0800, Justin Patrin wrote:
> On 2/20/07, Richard Purdie <rpurdie@rpsys.net> wrote:
> > Anyone watching mainline kernels will note that ARM kexec support got
> > merged and will be in 2.6.21 which is good. The issue is that the
> > syscall number had to change since the one its using at the moment is a
> > big hack.
> >
> > This means we will have to change kexec-tools and at that point it
> > becomes incompatible with older kernels.
> >
> > We can wait a bit and change when 2.6.21 is released, or update all our
> > patches now to use the new proper syscall number and update OE now.
> >
> > I know the NSLU2 people are users of this and would value their input.
> >
> 
> I use kexec on my Zaurus to test new kernels (and run multiple "ROM"s)
> so I'd be ineterested in the fix as well. I don't particularly care
> how it's done, though. Please let the list know again once something
> is decided and done. :-)

After discussion with the NSLU2 people, it was agreed we should just get
on with it. I've updated the zaurus kernels (linux-rp) and kexec-tools
itself. The NSLU2 kernels will follow. Anyone else using ARM kexec needs
to ensure their kernel uses the new syscall number 347.

OE users should ensure their kernels and kexec-tools versions match.

Regards,

Richard




  reply	other threads:[~2007-02-21  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 22:31 Impending Kexec interface change Richard Purdie
2007-02-20 22:36 ` Justin Patrin
2007-02-21  0:39   ` Richard Purdie [this message]
2007-02-20 23:42 ` Rod Whitby

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=1172018393.5884.122.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.