All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/10] sbc8560: Add v1 device tree source for Wind River SBC8560 board
Date: Tue, 5 Feb 2008 13:40:49 +1100	[thread overview]
Message-ID: <20080205024049.GC28846@localhost.localdomain> (raw)
In-Reply-To: <FF018A8D-21AC-4F05-887B-66B99A0D444C@kernel.crashing.org>

On Fri, Feb 01, 2008 at 08:46:32AM -0600, Kumar Gala wrote:
> 
> On Feb 1, 2008, at 1:54 AM, David Gibson wrote:
> 
> > On Thu, Jan 24, 2008 at 06:41:24PM -0500, Paul Gortmaker wrote:
[snip]
> >> +		epld@5,0 {
> >
> > I'm not entirely convinced on this two-level representation.  I think
> > the FSL people need to get together and define a binding (or set of
> > bindings) for their various chipselect style external bus bridges.
> 
> It seems reasonable if you had a FPGA off of the localbus to have a  
> two level representation.  One for the localbus controller on the FSL  
> part and the child to describe the FPGA.
> 
> What are you expecting beyond what we have today?  I guess I'm asking  
> what's missing from the localbus nodes we have?

Sorry, I was probably misleading.  All I really meant is that I don't
know enough about these FSL bus bridge arrangements to assess if this
representation is the most sensible one.  I'm presuming that this
chipselect bridge unit is a more-or-less standard ASIC appearing on
lots of the FSL chips, so it would be nice to have a standard binding
for them, as we do for the roughly-equivalent EBC bridge on 4xx.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2008-02-05  2:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 23:41 [PATCH 0/10] Support for SBC834x/8548/8560 Wind River Boards Paul Gortmaker
2008-01-24 23:41 ` [PATCH 1/10] sbc8560: add support for Wind River SBC8560 in arch/powerpc Paul Gortmaker
2008-01-24 23:41   ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 2/10] sbc8560: Add v1 device tree source for Wind River SBC8560 board Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-02-01  7:54     ` David Gibson
2008-02-01 14:46       ` Kumar Gala
2008-02-05  2:40         ` David Gibson [this message]
2008-02-05 15:44           ` Kumar Gala
2008-02-06  1:06             ` David Gibson
2008-02-05 16:53       ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 3/10] CPM2: Make support for the CPM2 optional on 8560 based boards Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-25  0:15       ` Scott Wood
2008-01-25  0:20         ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 4/10] sbc8560: Add default .config file for Wind River SBC8560 Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 5/10] sbc8548: Add basic support for Wind River SBC8548 as powerpc Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 6/10] sbc8548: Add v1 device tree source for Wind River SBC8548 board Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 7/10] sbc8548: Add default .config file for Wind River SBC8548 Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 8/10] sbc834x: Add support for Wind River SBC834x boards Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 9/10] sbc834x: Add device tree source for Wind River SBC834x board Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-24 23:41   ` [PATCH 10/10] sbc834x: Add default config file for Wind River SBC8349 board Paul Gortmaker
2008-01-24 23:41     ` Paul Gortmaker
2008-01-25  8:38 ` [PATCH 0/10] Support for SBC834x/8548/8560 Wind River Boards Kumar Gala

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=20080205024049.GC28846@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paul.gortmaker@windriver.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.