From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: linuxppc-dev@ozlabs.org
Cc: kexec@lists.infradead.org
Subject: [RFC] kexec support on Book-e, ppc32
Date: Wed, 1 Oct 2008 23:20:21 +0200 [thread overview]
Message-ID: <1222896024-22172-1-git-send-email-sebastian@breakpoint.cc> (raw)
This is what I am currently using for kexec support on mpc8544 / Book-E.
The userland (patch #3) behaves similar to the ppc64 code. Purgatory is
available and the user can specify new device tree. In v2wrap.S the setup
of the stack is disabled. I'm not sure why but as soon as I enable it,
the kernel does not appear. I think that I'm loading the value from the
wrong address but the same code is working for the kernel entry point.
Patch #1 adds support for the kernel. I've extended the misc32 code
because I did not want to copy the move_page_code.
Patch #2 adds the required callbacks to platform code of 8544ds
Sebastian
next reply other threads:[~2008-10-01 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 21:20 Sebastian Andrzej Siewior [this message]
2008-10-01 21:20 ` [RFC] powerpc: add kexec support on Book-E Sebastian Andrzej Siewior
2008-10-10 3:53 ` Benjamin Herrenschmidt
2008-10-12 13:55 ` Sebastian Andrzej Siewior
2008-10-01 21:20 ` [RFC] powerpc: enable kexec support on mpc8544ds Sebastian Andrzej Siewior
2008-10-01 21:20 ` [PATCH] powerpc: dtb and purgatory support for ppc32 Sebastian Andrzej Siewior
2008-10-02 3:54 ` Kumar Gala
2008-10-02 7:50 ` Sebastian Siewior
2008-10-02 10:05 ` Simon Horman
2008-10-03 5:44 ` Mohan Kumar M
2008-10-02 12:52 ` Kumar Gala
2008-10-02 13:03 ` Sebastian Andrzej Siewior
2008-10-08 3:03 ` Simon Horman
2008-10-12 13:39 ` Sebastian Andrzej Siewior
2008-10-15 3:37 ` Simon Horman
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=1222896024-22172-1-git-send-email-sebastian@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).