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


-------- Original-Nachricht --------
Datum: Tue, 19 Jun 2007 08:08:42 +0200
Von: Segher Boessenkool <segher@kernel.crashing.org>
An: "Gerhard Pircher" <gerhard_pircher@gmx.net>
CC: ppcdev list <linuxppc-dev@ozlabs.org>
Betreff: Re: [RFC] Device tree for new desktop platform in arch/powerpc

> Just name the cpu nodes "cpu@0" etc.  The "generic names"
> recommended practice wants this, and the node names here
> aren't actually used by anything anyway, except they look
> nice to the user.  The PowerPC ISA binding predates the
> generic names r.p. btw.
Good! That simplifies the (yet to be written) amigaone-cuboot.c
bootwrapper code a lot.

> > 3. The dts files define the device_type of a serial port as "serial", 
> > whereas the OF spec says "pnpPNP,501". What's the difference between 
> > the two?
> 
> "device_type" is "serial", "compatible" is "pnpPNP,whatever".
Sorry, I was thinking about compatible = "ns16550" and
compatible = "pnp..", but wrote device_type = "serial".
What's the difference between "ns16550" and "pnpPNP,501"?

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

or

Quote from the document:
>  "compatible" S
> Standard property name, specifies device names with which this
> device is compatible.
> 
> The meaning of this property is as defined in Open Firmware,
> as modified by the Generic Names Recommended Practice [7]. As
> described in those documents, the entries are a list of device
> names with which this device is compatible, starting with the
> name of the device itself and progressing through successively
> less precise and possibly less functional compatible devices.
> 
> For this device, the compatible property shall include "pnpPNP,501."
- End -

> "name" = "device_type" = "interrupt-controller".
> "compatible" is one of those pnpPNP things.

Quote from the "CHRP(TM) ISA Interrupt Controller Device
Binding" document:
> "compatible" S
> Standard property name, specifies device names with which
> this device is compatible.
> ....
> The compatible property shall include "chrp,iic."
- End -

I couldn't find any reference about a "pnp..." value for an i8259
interrupt controller. Is there already a generic function within the
kernel that can setup the interrupt controller based solely on the
information in the device tree?

> Please send the thing inline, not as an attachment.
Okay, will do so next time.

Thanks!

regards,

Gerhard
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

  reply	other threads:[~2007-06-19  9:08 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 [this message]
2007-06-19  9:28     ` Segher Boessenkool
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=20070619090816.55840@gmx.net \
    --to=gerhard_pircher@gmx.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).