linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "M B" <super.firetwister@googlemail.com>
To: jwboyer@linux.vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] add a simple 405EP based board
Date: Thu, 21 Aug 2008 14:46:32 +0200	[thread overview]
Message-ID: <6a6049b80808210546k51728cd2mf47c73487fe5033f@mail.gmail.com> (raw)
In-Reply-To: <1219319729.26429.40.camel@jdub.homelinux.org>

On 8/21/08, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:

> I plan on adding more 405 board support very soon.  When I do, it'll be
> along the lines of the patch series I just sent out for 44x.  There's
> really no reason to have a per CPU/board file if we can avoid it.
>
> Your code is simple enough overall, so I might even use it as a starting

>

I've seen your patches for 44x support and I like the idea of a
general board setup.
I wanted to make the dts public, because I needed some help to figure
out the "mdio-device" tag. So if you have further use for this you're
welcome.

> Though it's incomplete
> in that you have a DTS that requires something to poke values into it,
> and nothing readily apparent to do so.  A cuImage wrapper is probably
> warranted here.

The missing values in the dts get filled in by ft_cpu_setup(...) from
uboot, it's generic code and not board specific, but the board setup
in u-boot must call it, so it won't work for all boards.

Best regards

Markus

  reply	other threads:[~2008-08-21 12:53 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 [this message]
2008-08-21 13:42   ` Arnd Bergmann
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=6a6049b80808210546k51728cd2mf47c73487fe5033f@mail.gmail.com \
    --to=super.firetwister@googlemail.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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).