All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
	"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	"debayang. qdt" <debayang.qdt@qualcommdatacenter.com>
Subject: Re: Correct use of Arm related names
Date: Wed, 10 Oct 2018 10:48:51 +0200	[thread overview]
Message-ID: <4526903.3jovrJyB05@xps> (raw)
In-Reply-To: <AM6PR08MB3672075F241CEAA02C6CF58F98E00@AM6PR08MB3672.eurprd08.prod.outlook.com>

10/10/2018 06:37, Honnappa Nagarahalli:
> Hi,
> This email was triggered by a request to change ARM to Arm in the dpdk.org webpage. I went down the path of finding out the correct names to use. There has not been consistency in using these names across all other projects. So, the recommendation I have got is, 'choose something and use it consistently' (within the DPDK project). Following are my recommendations (please notice the lower/upper case of the letters):
> 
> Architectural State:
> aarch64/arm64 - referring to aarch64 state - recommended: aarch64
> aarch32/arm32 - referring to aarch32 state - recommended: aarch32 (arm32 might create confusion with armv7)
> 
> ISA:
> armv8.x
> armv7.x
> 
> Any reference to Company name:
> Arm
> 
> So, everything is lower case except when referring to the company (for ex: Copyright) name.
> 
> Please let me know if you have any questions.

There is still confusion about when to use the arch name (aarch64)
or the ISA (armv8)?

For instance, the lib/librte_eal/common/include/arch/arm/ directory
has files split by 32/64 arch. I thought it would make more sense to have
different low-level routines depending of the ISA.

Is it possible to have armv7 in aarch64?
Is it possible to have armv8 in aarch32?

      parent reply	other threads:[~2018-10-10  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  4:37 Correct use of Arm related names Honnappa Nagarahalli
2018-10-10  4:39 ` Honnappa Nagarahalli
2018-10-10  8:48 ` Thomas Monjalon [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=4526903.3jovrJyB05@xps \
    --to=thomas@monjalon.net \
    --cc=Gavin.Hu@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=debayang.qdt@qualcommdatacenter.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    /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.