From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Alexey Kardashevisky" <aik@au1.ibm.com>,
QEMU <qemu-devel@nongnu.org>, qemu-ppc <qemu-ppc@nongnu.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Prerna Saxena" <prerna@linux.vnet.ibm.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/2] [v3] target-ppc: Enhance CPU nodes of device tree to be PAPR compliant.
Date: Mon, 12 Aug 2013 21:17:26 +0200 [thread overview]
Message-ID: <20130812211726.7121a5da@thhw500> (raw)
In-Reply-To: <1376287404.32100.153.camel@pasglop>
Am Mon, 12 Aug 2013 16:03:24 +1000
schrieb Benjamin Herrenschmidt <benh@kernel.crashing.org>:
> On Mon, 2013-08-12 at 10:07 +0530, Prerna Saxena wrote:
>
> .../...
>
> > I dont know what context lead to this observation.
> > However, PAPR mentions the following nomenclature guideline:
> >
> > "The value of this property shall be of the form: “PowerPC,<name>”,
> > where <name> is the name of the processor chip which may be displayed to
> > the user. <name> shall not contain underscores."
>
> This actually comes from the original Open Firmware binding for PowerPC
> processors, which PAPR inherits largely from. Thus this naming scheme
> should apply to all PowerPC processors when a device-tree is involved.
Well, I think it should be used when an Open Firmware environment is
used. When you boot via ePAPR device tree, the name should be "cpu"
instead, according to the ePAPR specification.
Thomas
next prev parent reply other threads:[~2013-08-12 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 7:21 [Qemu-devel] [PATCH 0/2] [v3] target-ppc: Enhance CPU nodes of SPAPR-generated device tree Prerna Saxena
2013-08-08 7:24 ` [Qemu-devel] [PATCH 1/2] [v3] target-ppc: Get CPU name to correct reflect its model in the SLOF " Prerna Saxena
2013-08-08 7:26 ` [Qemu-devel] [PATCH 2/2] [v3] target-ppc: Enhance CPU nodes of device tree to be PAPR compliant Prerna Saxena
2013-08-08 10:34 ` Andreas Färber
2013-08-12 4:37 ` Prerna Saxena
2013-08-12 6:03 ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2013-08-12 19:17 ` Thomas Huth [this message]
2013-08-12 21:22 ` Benjamin Herrenschmidt
2013-08-14 10:18 ` Alexander Graf
2013-08-14 10:31 ` Andreas Färber
2013-08-14 11:04 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 11:20 Jacques Mony
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=20130812211726.7121a5da@thhw500 \
--to=thuth@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=aik@au1.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=benh@kernel.crashing.org \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).