From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Segher Boessenkool" <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] add Phytec pcm030 board support
Date: Mon, 5 May 2008 13:38:30 -0600 [thread overview]
Message-ID: <fa686aa40805051238n7df0c24fmc9fabeef4b7f6c63@mail.gmail.com> (raw)
In-Reply-To: <1328d38bed8a830af756850bbaf2e8ad@kernel.crashing.org>
On Mon, May 5, 2008 at 12:06 PM, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> >
> > > Add board support for the Phytec pcm030 mpc5200b based board. It
> > > does not need any platform specific fixups and as such is handled
> > > as a mpc5200 simple platform.
> > >
> >
> > Those still whingeing about how horrible and hard and tedious the new
> > world of device trees is, take note. We've certainly had some
> > teething problems as we all figure out how to use the device tree
> > properly. But this is the payoff: support for a new board added with
> > one text file. It's only going to get more common.
> >
>
> /me imagines a world where every sane device (not just PowerPC)
> uses OF device trees...
PowerPC? check.
Sparc? check.
Microblaze? check.
its just a matter of taking them out one at a time. :-P
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-05-05 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 13:48 [PATCH] add Phytec pcm030 board support Sascha Hauer
2008-05-05 1:16 ` David Gibson
2008-05-05 15:59 ` Grant Likely
2008-05-05 18:06 ` Segher Boessenkool
2008-05-05 19:38 ` Grant Likely [this message]
2008-05-06 4:06 ` Stephen Rothwell
2008-05-06 5:51 ` Segher Boessenkool
2008-05-06 7:20 ` Stephen Rothwell
2008-05-05 17:01 ` Jon Smirl
2008-05-05 17:08 ` Grant Likely
2008-05-05 17:22 ` Jon Smirl
2008-05-06 8:08 ` Sascha Hauer
2008-05-06 12:47 ` Jon Smirl
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=fa686aa40805051238n7df0c24fmc9fabeef4b7f6c63@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.org \
/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).