From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Tiejun Chen <tiejun.chen@windriver.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc/405ex: Support cuImage for PPC405EX
Date: Tue, 18 Aug 2009 09:28:35 -0400 [thread overview]
Message-ID: <20090818132835.GA2530@zod.rchland.ibm.com> (raw)
In-Reply-To: <1250562484-16415-1-git-send-email-tiejun.chen@windriver.com>
On Tue, Aug 18, 2009 at 10:28:02AM +0800, Tiejun Chen wrote:
>Summary: powerpc/405ex: Support cuImage for PPC405EX
>Reviewers: Benjmain and linux-ppc
>----------------------------------------------------
>These patch series are used to support cuImage on the kilauea board based on PPC405ex.
>
>Tested on the amcc kilauea board:
Hm. The U-Boot version that ships on the AMCC Kilauea board is FDT aware, so
cuImage shouldn't be needed at all. I'm slightly confused why we need this.
Are you using it for some other board derived from 405EX that doesn't have
an FDT aware U-Boot?
josh
next prev parent reply other threads:[~2009-08-18 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 2:28 powerpc/405ex: Support cuImage for PPC405EX Tiejun Chen
2009-08-18 2:28 ` [PATCH 1/2] powerpc/405ex: provide necessary fixup function to support cuImage Tiejun Chen
2009-08-20 13:26 ` Josh Boyer
2009-08-21 6:00 ` tiejun.chen
2009-08-21 11:49 ` Josh Boyer
2009-08-18 2:28 ` [PATCH 2/2] powerpc/405ex: support cuImage via included dtb Tiejun Chen
2009-08-20 13:31 ` Josh Boyer
2009-08-21 5:41 ` tiejun.chen
2009-08-21 6:35 ` Stefan Roese
2009-08-21 6:39 ` tiejun.chen
2009-08-21 11:49 ` Josh Boyer
2009-08-18 3:30 ` Mailing lists (Was: Re: powerpc/405ex: Support cuImage for PPC405EX) Stephen Rothwell
2009-08-18 4:38 ` tiejun.chen
2009-08-18 3:39 ` powerpc/405ex: Support cuImage for PPC405EX Benjamin Herrenschmidt
2009-08-18 13:28 ` Josh Boyer [this message]
2009-08-19 1:45 ` tiejun.chen
2009-08-19 11:45 ` Josh Boyer
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=20090818132835.GA2530@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tiejun.chen@windriver.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;
as well as URLs for NNTP newsgroup(s).