LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: Add support for OpenBlockS 600
Date: Fri, 02 Dec 2011 19:49:09 +1100	[thread overview]
Message-ID: <1322815749.11728.8.camel@pasglop> (raw)
In-Reply-To: <CAOesGMgkh-OzyRH_O+2TT7AzhY0bHWazua9s6Mj9qmb174DANw@mail.gmail.com>

On Thu, 2011-12-01 at 22:40 -0800, Olof Johansson wrote:
> Hi,
> 
> On Thu, Dec 1, 2011 at 9:35 PM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> 
> >  arch/powerpc/boot/dts/obs600.dts           |  314 ++++++++++++++++++++++++++++
> 
> It'd be nice to have dtsi files for the SoCs, there's a lot of boiler
> plate in there. That shouldn't hold up this specific patch though.

Right definitely. One thing that I wonder tho (I haven't looked at the
dtsi stuff specifically), can it "remove" a node ?

Ie. The 405EX dtsi will probably expose the PCIe bridges in that
specific case, but I want them out as they aren't wired and trying to
use them causes a hang on this board.

Another approach is to stick in a disabled property and make sure the
ppc4xx_pci code checks it.

> >  arch/powerpc/boot/wrapper                  |   22 ++-
> >  arch/powerpc/configs/40x/obs600_defconfig  |   83 ++++++++
> 
> A new single-board defconfig? On arm that is a strong NACK, I'd say
> it's a bad idea on powerpc as well.

The defconfigs are just there for the user sake, I find them handy
myself. I have no objection (as maintainer) to having them since
nowadays they are really small and can be handy for embedded systems
(ie, on a tiny 405 based machine you really want to cut out the bloat
you don't need).

As long as the board -can- be built as part of a combo that is.

So as maintainer, I think I'll keep applying a different policy than ARM
in that area ;-)

Cheers,
Ben.

  reply	other threads:[~2011-12-02  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  5:35 [PATCH] powerpc: Add support for OpenBlockS 600 Benjamin Herrenschmidt
2011-12-02  6:40 ` Olof Johansson
2011-12-02  8:49   ` Benjamin Herrenschmidt [this message]
2011-12-02 11:52   ` Josh Boyer

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=1322815749.11728.8.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=olof@lixom.net \
    /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