From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/6] bootwrapper: Add support for cuboot platforms.
Date: Fri, 23 Mar 2007 16:25:40 +1100 [thread overview]
Message-ID: <20070323052540.GB6199@localhost.localdomain> (raw)
In-Reply-To: <20070322194924.GC31965@ld0162-tx32.am.freescale.net>
On Thu, Mar 22, 2007 at 02:49:24PM -0500, Scott Wood wrote:
> Platforms beginning with "cuboot" have the bootwrapper code built in,
> unlike the regular uboot platform.
I think 3, 4 and 5 of this series should be merged into a single
patch. They're not much use without each other.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-03-23 5:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 19:46 [PATCH 0/6] bootwrapper/cuboot Scott Wood
2007-03-22 19:49 ` [PATCH 1/6] bootwrapper: Add dt_xlate_reg(), and use it to find serial registers Scott Wood
2007-03-22 19:49 ` [PATCH 2/6] bootwrapper: Add ppcboot.h Scott Wood
2007-03-22 19:49 ` [PATCH 3/6] bootwrapper: Add support for cuboot platforms Scott Wood
2007-03-23 5:25 ` David Gibson [this message]
2007-03-22 19:49 ` [PATCH 4/6] bootwrapper: Add CONFIG_DEVICE_TREE Scott Wood
2007-03-22 19:49 ` [PATCH 5/6] bootwrapper: Add a cuImage target Scott Wood
2007-03-23 5:40 ` David Gibson
2007-03-23 15:18 ` Scott Wood
2007-03-23 23:39 ` David Gibson
2007-03-22 19:49 ` [PATCH 6/6] bootwrapper: cuboot for 83xx Scott Wood
2007-03-23 5:54 ` David Gibson
2007-03-23 15:30 ` Scott Wood
2007-03-23 23:37 ` David Gibson
2007-03-26 15:53 ` Scott Wood
2007-04-04 2:06 ` Mark A. Greer
2007-04-04 6:38 ` David Gibson
2007-04-04 16:01 ` Mark A. Greer
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=20070323052540.GB6199@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).