All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Gerhard Pircher" <gerhard_pircher@gmx.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Device tree for new desktop platform in arch/powerpc
Date: Tue, 19 Jun 2007 11:28:47 +0200	[thread overview]
Message-ID: <956019fbf071a89518ccfdd8799cf5c2@kernel.crashing.org> (raw)
In-Reply-To: <20070619090816.55840@gmx.net>

>> Where in the OF specs did you find this pnpPNP thing btw?
> See here:
> http://playground.sun.com/1275/bindings/devices/html/serial.html

Ah, the CHRP stuff I so happily ignore.

The generic pnpPNP thing is described in the ISA binding,
4.1.1 "name".  You should put this into "compatible"
though, since generic names are preferred.

>> "compatible" is one of those pnpPNP things.
>
> Quote from the "CHRP(TM) ISA Interrupt Controller Device
> Binding" document:

But you're not CHRP.  This is an ISA device however,
so you should follow the ISA binding.

> I couldn't find any reference about a "pnp..." value for an i8259
> interrupt controller.

pnpPNP,0 for AT-style, pnpPNP,1 for EISA-style.

It is quite hard to find a list of the standard PNP
device code.  Here's a link, grab it before the file
disappears forever:

<http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a 
-923143f3456c/devids.txt>

> Is there already a generic function within the
> kernel that can setup the interrupt controller based solely on the
> information in the device tree?

Probably not.  There are bits and pieces though, your
job is to glue it all together.  You can handle this
in your platform code, if people want to make it more
generic they can always refactor the code ;-)


Segher

  reply	other threads:[~2007-06-19  9:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 18:57 [RFC] Device tree for new desktop platform in arch/powerpc Gerhard Pircher
2007-06-18 19:15 ` Mark A. Greer
2007-06-18 19:43   ` Gerhard Pircher
2007-06-18 20:25     ` Mark A. Greer
2007-06-19  5:08       ` David Gibson
2007-06-19  5:42 ` David Gibson
2007-06-19  6:16   ` Segher Boessenkool
2007-06-19  8:40   ` Gerhard Pircher
2007-06-19  9:14     ` Segher Boessenkool
2007-06-19  9:52       ` Gerhard Pircher
2007-06-19 10:08         ` Segher Boessenkool
2007-06-19 12:37           ` Gerhard Pircher
2007-06-19 13:15             ` Segher Boessenkool
2007-06-19 13:29               ` Gerhard Pircher
2007-06-21 12:42   ` Benjamin Herrenschmidt
2007-06-21 13:28     ` Gerhard Pircher
2007-06-21 14:59       ` Segher Boessenkool
2007-06-21 14:29     ` Segher Boessenkool
2007-06-21 23:25       ` Benjamin Herrenschmidt
2007-06-22  7:52         ` Segher Boessenkool
2007-06-22  8:16           ` Benjamin Herrenschmidt
2007-06-22  9:10             ` Segher Boessenkool
2007-06-19  6:08 ` Segher Boessenkool
2007-06-19  9:08   ` Gerhard Pircher
2007-06-19  9:28     ` Segher Boessenkool [this message]
2007-06-21 12:36 ` Benjamin Herrenschmidt
2007-06-21 13:20   ` Gerhard Pircher
2007-06-21 14:38     ` Segher Boessenkool
2007-06-21 16:27       ` Gerhard Pircher
2007-06-21 23:22     ` Benjamin Herrenschmidt
2007-06-22 13:12       ` Gerhard Pircher
2007-06-22 13:40         ` Benjamin Herrenschmidt
2007-06-21 14:24   ` Segher Boessenkool
2007-06-21 16:21     ` Gerhard Pircher

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=956019fbf071a89518ccfdd8799cf5c2@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gerhard_pircher@gmx.net \
    --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 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.