linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add 85xx CDS to arch/powerpc
Date: Mon, 3 Apr 2006 23:27:39 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0604032326320.9767-100000@gate.crashing.org> (raw)
In-Reply-To: <E1FQBs8-00061K-BI@jdl.com>

On Sun, 2 Apr 2006, Jon Loeliger wrote:

> So, like, the other day Arnd Bergmann mumbled:
> > [MPIC]
> > 
> > Shouldn't all this come from the device tree?
> > 
> > ...
> >
> > > +/* PCI interrupt controller */
> > > +#define PIRQ0A			MPC85xx_IRQ_EXT0
> > > +#define PIRQ0B			MPC85xx_IRQ_EXT1
> > > +#define PIRQ0C			MPC85xx_IRQ_EXT2
> > > +#define PIRQ0D			MPC85xx_IRQ_EXT3
> > > +#define PIRQ1A			MPC85xx_IRQ_EXT11
> > 
> > And these as well, more importantly?
> 
> Yep.  In time they will.  However, the parsing of the
> PIC nodes hasn't been added to the 85xx (uh, nor 83xx)
> as of yet.
> 
> It is on "the list".
> 
> We should defer to Kumar to accepting these at this stage
> or not.

As Jon stated its on the list.  We need to work up something like what we 
have for parsing memory addresses for irqs.  Ben has some ideas, until 
then we make forward progress using the old style of things.

- k

      reply	other threads:[~2006-04-04  4:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02 22:42 [PATCH] Add 85xx CDS to arch/powerpc Andy Fleming
2006-04-02 23:00 ` Arnd Bergmann
2006-04-02 23:20   ` Jon Loeliger
2006-04-04  4:27     ` Kumar Gala [this message]

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=Pine.LNX.4.44.0604032326320.9767-100000@gate.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=paulus@samba.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).