From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: sprinkled references to "powerpc" vs "ppc" in adt-installer
Date: Mon, 17 Dec 2012 09:21:29 -0600 [thread overview]
Message-ID: <50CF3879.2070809@windriver.com> (raw)
In-Reply-To: <20121217075238.GA4305@mi.fu-berlin.de>
On 12/17/12 1:52 AM, Henning Heinold wrote:
> On Sun, Dec 16, 2012 at 04:11:15PM -0500, Bill Traynor wrote:
>> On Dec 16, 2012 5:57 AM, "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
>>>
>>>
>>> perusing adt-installer recipe and files and i notice there are a few
>>> mentions of "powerpc" whereas it seems that "ppc" is the correct
>>> architecture abbreviation. obviously doesn't hurt anything but it
>>> might be confusing for people reading the source.
>>
>> Isn't the architecture just called Power now?
>
> Nope, POWER is the midiron architecture from IBM, where POWERPC is a subset of POWER.
From power.org:
> What is happening to the PowerPC wordmark and logo?
> The PowerPC wordmark, as referencing the PowerPC instruction set architecture (ISA) and products based on that ISA, will continue to exist. However, we encourage everyone to use the new Power Architecture trademark and the new logos to help establish a more consistent voice in the marketplace for the Power Architecture platform.
In otherwords when talking about the overall architecture platform "Power" is
correct. When referring to the specific (older) PowerPC ISA, PowerPC is acceptable.
The way I've done it is, depending on usage, either refer to it as "Power" (i.a.
ia32, MIPS, ARM) when discussing the 'architecture family'. (The FAQ item above
seems to indicate 'Power' is the right term.) "PowerPC" is still used when
talking about older processors...
"powerpc" when talking about the GNU architecture, and 'ppc' when abreviating
the GNU architecture (such as a package arch, CPU tuning, etc.) Much of it is
historical so you should see all three (or four) terms used through the
documentation when discussing different parts.
--Mark
> Bye Henning.
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2012-12-17 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 10:56 sprinkled references to "powerpc" vs "ppc" in adt-installer Robert P. J. Day
2012-12-16 21:11 ` Bill Traynor
2012-12-17 7:52 ` Henning Heinold
2012-12-17 15:21 ` Mark Hatle [this message]
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=50CF3879.2070809@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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