public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v9 0/31] Create generic board init for ARM, x86, PPC
Date: Fri, 15 Mar 2013 18:23:22 -0400	[thread overview]
Message-ID: <20130315222322.GA11084@bill-the-cat> (raw)
In-Reply-To: <20130313084626.8B1CD20057C@gemini.denx.de>

On Wed, Mar 13, 2013 at 09:46:26AM +0100, Wolfgang Denk wrote:
> Dear Simon Glass,
> 
> In message <1363020460-14307-1-git-send-email-sjg@chromium.org> you wrote:
> > This series creates a generic board init implementation which contains
> > the essential functions of the major arch/xxx/lib/board.c files. It is
> > split into two parts: board_f.c for pre-relocation and board_r.c for
> > post-relocation.
> ...
> > ARM is a relatively large board.c file and one which I can test, therefore
> > I think it is a good target for this series. On the other hand, x86 is
> > relatively small and simple, but different enough that it introduces a
> > few issues to be solved. So I have chosen both ARM and x86 for this series.
> > After a suggestion from Wolfgang I have added PPC also. This is the
> > largest and most feature-full board, so hopefully we have all bases
> > covered in this series. Other archs are mostly a subset of these.
> 
> I did some testing on Power Architecture systems - to be precise:
> 
> CPU		Board
> --------------------------
> MPC860T		TQM860L
> MPC5200		TQM5200S
> PPC405EX	Kilauea
> PPC440EP	Yosemite
> PPC440EX	Sequoia
> PPC440SPe	Katmai
> PPC460EX	Canyonlands
> 
> On all boards I verified at least environment access (printenv,
> saveenv) and network operation (TFTP download); where available also
> PCI.  Everything appears to work fine, no problems noted.
> 
> A well done job, thanks a lot!
> 
> For the whole series:
> 
> Tested-by: Wolfgang Denk <wd@denx.de>
> Acked-by: Wolfgang Denk <wd@denx.de>

OK, I've taken http://patchwork.ozlabs.org/bundle/sjg/us-board/ but with
http://patchwork.ozlabs.org/patch/228080/ for 2/31 and applied this to
u-boot/master now, thanks again!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130315/da1bf0d1/attachment.pgp>

  reply	other threads:[~2013-03-15 22:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1363020460-14307-1-git-send-email-sjg@chromium.org>
2013-03-11 16:49 ` [U-Boot] [PATCH v9 09/31] Introduce generic pre-relocation board_f.c Simon Glass
2013-03-11 16:49   ` [U-Boot] [PATCH v9 13/31] arm: Enable generic board support Simon Glass
2013-03-11 16:50   ` [U-Boot] [PATCH v9 17/31] ppc: " Simon Glass
2013-03-11 16:50   ` [U-Boot] [PATCH v9 21/31] x86: " Simon Glass
2013-03-13  8:46   ` [U-Boot] [PATCH v9 0/31] Create generic board init for ARM, x86, PPC Wolfgang Denk
2013-03-15 22:23     ` Tom Rini [this message]
2013-03-30 21:34     ` Simon Glass
     [not found] <1363021453-6566-1-git-send-email-sjg@chromium.org>
2013-03-11 17:50 ` Simon Glass
2013-03-13  3:52 ` Simon Glass
2013-03-13 13:16   ` Andreas Bießmann
2013-03-13 16:25     ` Tom Rini
2013-03-13 22:20       ` Simon Glass
2013-03-14 17:42         ` Simon Glass

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=20130315222322.GA11084@bill-the-cat \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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