All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org, jwboyer@linux.vnet.ibm.com
Cc: Markus Brunner <super.firetwister@googlemail.com>
Subject: Re: [PATCH] add a simple 405EP based board
Date: Thu, 21 Aug 2008 15:42:37 +0200	[thread overview]
Message-ID: <200808211542.38395.arnd@arndb.de> (raw)
In-Reply-To: <1219319729.26429.40.camel@jdub.homelinux.org>

On Thursday 21 August 2008, Josh Boyer wrote:
> On Thu, 2008-08-21 at 10:07 +0200, Markus Brunner wrote:
> > This adds support for a simple ppc405ep board.=20
> > At the moment, there are no 405ep boards in arch/powerpc, so this can b=
e used as a template
> > for new boards, or migrating them from arch/ppc.
> > I2c, UART and EMAC are working. PCI could not be tested, so it was not =
included in the dts.
>=20
> I plan on adding more 405 board support very soon. =A0When I do, it'll be
> along the lines of the patch series I just sent out for 44x. =A0There's
> really no reason to have a per CPU/board file if we can avoid it.
>=20

This may be a stupid question, but is there really a reason to keep 40x and=
 44x
setup files separate? AFAICT, the ppc_md structures are the same, so even y=
ou
can never have a common binary between 40x and 44x, you may have the same p=
latform
file.

	Arnd <><

  parent reply	other threads:[~2008-08-21 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  8:07 [PATCH] add a simple 405EP based board Markus Brunner
2008-08-21  8:52 ` Stephen Rothwell
2008-08-21 11:55 ` Josh Boyer
2008-08-21 12:46   ` M B
2008-08-21 13:42   ` Arnd Bergmann [this message]
2008-08-21 16:10     ` Josh Boyer
2008-08-22 12:39       ` Arnd Bergmann
2008-08-26  0:41 ` David Gibson

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=200808211542.38395.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=super.firetwister@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.