From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34830) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9YMc-0002aJ-HT for qemu-devel@nongnu.org; Wed, 14 Aug 2013 06:31:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9YMU-0000UK-Gv for qemu-devel@nongnu.org; Wed, 14 Aug 2013 06:31:38 -0400 Message-ID: <520B5C80.4070100@suse.de> Date: Wed, 14 Aug 2013 12:31:28 +0200 From: =?windows-1252?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <20130808125106.6b29a78c@zephyr> <20130808125629.4e5f435d@zephyr> <5203743D.6060009@suse.de> <5208669A.7010000@linux.vnet.ibm.com> <1376287404.32100.153.camel@pasglop> <20130812211726.7121a5da@thhw500> <1376342545.32100.181.camel@pasglop> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/2] [v3] target-ppc: Enhance CPU nodes of device tree to be PAPR compliant. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Alexey Kardashevisky , Thomas Huth , QEMU , qemu-ppc , Anthony Liguori , Prerna Saxena Am 14.08.2013 12:18, schrieb Alexander Graf: >=20 > On 12.08.2013, at 23:22, Benjamin Herrenschmidt wrote: >=20 >> On Mon, 2013-08-12 at 21:17 +0200, Thomas Huth wrote: >>> Am Mon, 12 Aug 2013 16:03:24 +1000 >>> schrieb Benjamin Herrenschmidt : >>> >>>> 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: =93PowerPC,= =94, >>>>> where is the name of the processor chip which may be display= ed to >>>>> the user. shall not contain underscores." >>>> >>>> This actually comes from the original Open Firmware binding for Powe= rPC >>>> processors, which PAPR inherits largely from. Thus this naming schem= e >>>> should apply to all PowerPC processors when a device-tree is involve= d. >>> >>> 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. >> >> Yeah well ... this is a gratuituous change in ePAPR, I don't think it >> matters really what the name is anyway. I'd suggest sticking to the >> original OF binding. >=20 > Can't we just include the PowerPC, bit as part of the fw_name field in = the class? I don't think we have any CPUs that can be used both in ePAPR = and sPAPR environments. So the POWER7 fw_name field would just contain "P= owerPC,POWER7" and the device tree creation code merely appends the @%d p= iece. That's exactly what my patch series does, just be patient. :) Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg