From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/4] powerpc/85xx: Rename PowerPC core nodes to match other e500mc based .dts
Date: Fri, 2 Sep 2011 12:52:38 -0500 [thread overview]
Message-ID: <4E6117E6.8080103@freescale.com> (raw)
In-Reply-To: <0995BAB2-7865-4E95-A842-EFE486FFDAC4@kernel.crashing.org>
On 09/01/2011 10:21 PM, Kumar Gala wrote:
>
> On Sep 1, 2011, at 3:42 PM, Scott Wood wrote:
>
>> On 09/01/2011 02:26 PM, Kumar Gala wrote:
>>> The P4080 silicon device tree was using PowerPC,4080 while the other
>>> e500mc based SoCs used PowerPC,e500mc. Use the core name to be
>>> consistent going forward.
>>
>> Why are we not using the generic names recommendation?
>>
>> Is the "PowerPC" vendor string still appropriate here, or should we use
>> "fsl"?
>>
>> -Scott
>
> I have mixed feelings on this. The PowerPC,NAME has a long history & precedence. Is there any use or value to change this?
It's inconsistent with all of our other compatibles. My understanding
is that for older chips, the naming was from a managed numberspace -- is
"e500" or "eXXXX" something that was explicitly granted to us by
power.org, or just something we started calling our cores?
-Scott
next prev parent reply other threads:[~2011-09-02 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 19:26 [PATCH 1/4] powerpc/85xx: Rename PowerPC core nodes to match other e500mc based .dts Kumar Gala
2011-09-01 20:42 ` Scott Wood
2011-09-01 22:34 ` Tabi Timur-B04825
2011-09-02 3:21 ` Kumar Gala
2011-09-02 17:52 ` Scott Wood [this message]
2011-09-02 18:29 ` Kumar Gala
2011-09-02 18:33 ` Scott Wood
2011-09-01 22:33 ` Tabi Timur-B04825
2011-09-02 3:35 ` Kumar Gala
2011-10-12 4:21 ` Kumar Gala
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=4E6117E6.8080103@freescale.com \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.org \
--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.