linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur.tabi@calxeda.com>
Cc: Stef van Os <stef.van.os@prodrive.nl>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/1] powerpc/85xx: Board support for ppa8548
Date: Mon, 4 Feb 2013 10:34:12 -0600	[thread overview]
Message-ID: <1359995652.14901.0@snotra> (raw)
In-Reply-To: <CAOZdJXU6OFu1878s9rrNws3uqT_F7-GFS95ZJT5EZmw35=6hbQ@mail.gmail.com> (from timur.tabi@calxeda.com on Fri Feb  1 22:34:44 2013)

On 02/01/2013 10:34:44 PM, Timur Tabi wrote:
> On Fri, Feb 1, 2013 at 6:31 PM, Scott Wood <scottwood@freescale.com> =20
> wrote:
> >
> > I guess the reason you're not using fsl/mpc8548si-post.dtsi is that =20
> you
> > don't want PCI.  Maybe PCI and srio should be moved out of that =20
> file, or
> > ifdeffed if 85xx ever ends up using the preprocessor for its device =20
> trees.
>=20
> Wouldn't it be easier to add status=3D"disabled" in this dts file?  I do
> something similar with the LBC on the p1022rdk.
>=20
> 	board_lbc: lbc: localbus@ffe05000 {
> 		/* The P1022 RDK does not have any localbus devices */
> 		status =3D "disabled";
> 	};

Yeah, that'd work.

-Scott=

  reply	other threads:[~2013-02-04 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 15:36 [PATCH 1/1] powerpc/85xx: Board support for ppa8548 Stef van Os
2013-02-02  0:31 ` Scott Wood
2013-02-02  4:34   ` Timur Tabi
2013-02-04 16:34     ` Scott Wood [this message]
2013-02-02 19:25   ` Stef van Os
2013-02-02 20:24     ` Timur Tabi

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=1359995652.14901.0@snotra \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=stef.van.os@prodrive.nl \
    --cc=timur.tabi@calxeda.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 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).