From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Gerhard Pircher" <gerhard_pircher@gmx.net>
Cc: ppcdev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Device tree for new desktop platform in arch/powerpc
Date: Tue, 19 Jun 2007 08:08:42 +0200 [thread overview]
Message-ID: <136ef2695edbe7c8a535b5b4c7a669bf@kernel.crashing.org> (raw)
In-Reply-To: <20070618185715.321010@gmx.net>
[Your "To:" header was broken...]
> 1. The AmigaOne makes use of different G3 (750Cx, 750GL, 750GX) and G4
> (7400, 7450, 7455, 7457) CPUs. The current dts file defines a cpu node
> with the name "PowerPC,7xxx@0" and the bootwrapper just fills in the
> cpu-, bus- and timebase frequencies. Is this the recommended way, or
> should the bootwrapper create a fresh cpu node with the correct name
> of the CPU (e.g. "PowerPC,7455@ 0" - I guess this would require a
> table with all PVR values and their corresponding CPU name. Or is
> there a function in the kernel that do this?).
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.
> 2. I tried to define all ISA devices, which are integrated in the
> southbridge (VT82C686B). Currently these are child nodes of the device
> tree root.
This cannot work on PowerPC since PowerPC doesn't have
legacy I/O on the system bus.
> Should they be child nodes of the southbridge's PCI-to-ISA device node?
Yes.
> If so, where should I specify the register address ranges (reg
> property)? In the PCI device node or in the ISA device nodes, as it is
> now?
Both. Each device has a "reg" property that describes that
device's registers relative to the addressing on the bus it
sits on. All busses that do a direct one-to-one mapping of
some address range (perhaps with a translation) have a "ranges"
property describing that.
> 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".
Where in the OF specs did you find this pnpPNP thing btw?
> 4. I couldn't find any information for a device tree representation of
> the i8259 interrupt controller in the booting-without-of.txt file. Is
> my implementation correct (inspired by the OF documents)?
"name" = "device_type" = "interrupt-controller".
"compatible" is one of those pnpPNP things.
> I would be grateful, if you could take a look at my dts file and
> comment on every line that doesn't meet your views.
Please send the thing inline, not as an attachment.
Segher
next prev parent reply other threads:[~2007-06-19 6: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 [this message]
2007-06-19 9:08 ` Gerhard Pircher
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=136ef2695edbe7c8a535b5b4c7a669bf@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.