From: James Black <jblack547@gmail.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Linuxppc-dev@lists.ozlabs.org
Subject: Re: kexec for powerpc
Date: Thu, 12 Nov 2009 16:42:47 -0700 [thread overview]
Message-ID: <b77025b40911121542q2d318870i627b3cc4d8bb444b@mail.gmail.com> (raw)
In-Reply-To: <20091112233148.GF5699@hansolo.jdub.homelinux.org>
powerpc32 for processors like the freescale 82xx, 83xx machines.
Thanks,
JB
On Thu, Nov 12, 2009 at 4:31 PM, Josh Boyer <jwboyer@gmail.com> wrote:
> On Thu, Nov 12, 2009 at 04:08:07PM -0700, James Black wrote:
>>Are there efforts in this area or is it already working for powerpc? I
>>cross compiled kexec and tried it on an old kernel with kexec support
>>compiled in.
>
> 'powerpc' is a bit too vague. It works on lots of ppc64 machines already.
> What class of hardware are you talking about?
>
> josh
>
--
Jim Black
Senior Software Engineer
Aztek Networks, Inc.
2477 55th Street, Suite 202
Boulder, CO 80301
www.azteknetworks.com
next prev parent reply other threads:[~2009-11-12 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 23:08 kexec for powerpc James Black
2009-11-12 23:31 ` Josh Boyer
2009-11-12 23:42 ` James Black [this message]
2009-11-12 23:55 ` wilbur.chan
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=b77025b40911121542q2d318870i627b3cc4d8bb444b@mail.gmail.com \
--to=jblack547@gmail.com \
--cc=Linuxppc-dev@lists.ozlabs.org \
--cc=jwboyer@gmail.com \
/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