LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Matthew McClintock <msm@freescale.com>
Cc: muvarov@gmail.com, linuxppc-dev@lists.ozlabs.org,
	sebastian@breakpoint.cc, kexec@lists.infradead.org
Subject: Re: [PATCH v3 0/7] Fixup booting with device trees and uImage/elf on ppc32
Date: Tue, 27 Jul 2010 11:55:06 +0900	[thread overview]
Message-ID: <20100727025506.GA1944@verge.net.au> (raw)
In-Reply-To: <1279687384-9770-1-git-send-email-msm@freescale.com>

[Cced linuxppc-dev]

On Tue, Jul 20, 2010 at 11:42:57PM -0500, Matthew McClintock wrote:
> This patch series adds full support for booting with a flat device tree
> with either uImage or elf file formats. Kexec and Kdump should work, and
> you should also be able to use ramdisks or reuse your current ramdisk as well
> 
> This patch series was tested on an mpc85xx system with a kernel version
> 2.6.35-rc3
> 
> v1: Initial version
> 
> v2: Added support for fs2dt (file system to device tree)
> 
> v3: Fix some misc. git problems I had and other code cleanups

Hi Matthew,

I'm a little concerned that these changes are non trivial and haven't had
much review. But I am prepared to put them into my tree once 2.0.2 is
released - perhaps that way they will get some test coverage. Does
that work for you?

> 
> Matthew McClintock (7):
>   Restore kexec uImage-ppc to working state
>   Fix case where phys_addr_t != unsigned long when reading proc entries
>   Update uImage to support crash kernel and misc fixes
>   Update Elf-ppc to support crash kernel and misc fixes
>   Add support for ramdisk on ppc32 for uImage-ppc and Elf-ppc
>   Add support for reworking flat device tree support
>   Add documentation/howto for mpc85xx systems
> 
>  doc/mpc85xx.txt                       |  190 +++++++++++++++++++++
>  kexec/arch/ppc/Makefile               |    1 +
>  kexec/arch/ppc/fixup_dtb.c            |  298 ++++++++++++++++++++++++++++++++-
>  kexec/arch/ppc/fixup_dtb.h            |    6 +-
>  kexec/arch/ppc/include/arch/options.h |    3 +
>  kexec/arch/ppc/kexec-elf-ppc.c        |  186 +++++++++------------
>  kexec/arch/ppc/kexec-ppc.c            |  262 +++++++++++++++++------------
>  kexec/arch/ppc/kexec-ppc.h            |    3 +
>  kexec/arch/ppc/kexec-uImage-ppc.c     |  136 ++++++++++++---
>  kexec/arch/ppc/ops.h                  |    1 -
>  purgatory/arch/ppc/purgatory-ppc.c    |    5 +
>  11 files changed, 852 insertions(+), 239 deletions(-)
>  create mode 100644 doc/mpc85xx.txt
> 
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec

       reply	other threads:[~2010-07-27  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1279687384-9770-1-git-send-email-msm@freescale.com>
2010-07-27  2:55 ` Simon Horman [this message]
2010-07-27  3:59   ` [PATCH v3 0/7] Fixup booting with device trees and uImage/elf on ppc32 Maxim Uvarov
2010-07-27  4:22   ` Matthew McClintock
2010-07-29  9:18     ` 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=20100727025506.GA1944@verge.net.au \
    --to=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msm@freescale.com \
    --cc=muvarov@gmail.com \
    --cc=sebastian@breakpoint.cc \
    /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