public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Thomas Abraham <thomas.abraham@arm.com>
Cc: Jagadeesh Ujja <jagadeesh.ujja@arm.com>,
	 "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH edk2-platforms 0/2] Platforms/ARM/SgiPkg: apply product names for sgiclarka and sgiclarkh platforms
Date: Fri, 15 Mar 2019 13:29:18 +0100	[thread overview]
Message-ID: <CAKv+Gu8z6-YVhYu5x5GyG3-_RuU_Dw8uJnn9khp5Ai5tQ6QcBg@mail.gmail.com> (raw)
In-Reply-To: <CAJuA9ajbQ=qABNf1SDJm-ju51oDxsPd1QSMP5bwb_EPk081A7Q@mail.gmail.com>

On Fri, 15 Mar 2019 at 13:25, Thomas Abraham <thomas.abraham@arm.com> wrote:
>
> On Fri, Mar 15, 2019 at 5:27 PM Ard Biesheuvel
> <ard.biesheuvel@linaro.org> wrote:
> >
> > On Fri, 15 Mar 2019 at 12:40, Jagadeesh Ujja <jagadeesh.ujja@arm.com> wrote:
> > >
> > > On Fri, Mar 15, 2019 at 4:55 PM Ard Biesheuvel
> > > <ard.biesheuvel@linaro.org> wrote:
> > > >
> > > > On Fri, 15 Mar 2019 at 12:17, Jagadeesh Ujja <jagadeesh.ujja@arm.com> wrote:
> > > > >
> > > > > hi Ard,
> > > > >
> > > > > On Fri, Mar 15, 2019 at 4:14 PM Ard Biesheuvel
> > > > > <ard.biesheuvel@linaro.org> wrote:
> > > > > >
> > > > > > On Fri, 15 Mar 2019 at 09:21, Jagadeesh Ujja <jagadeesh.ujja@arm.com> wrote:
> > > > > > >
> > > > > > > hi Ard/Leif
> > > > > > >
> > > > > > > Please let me know if you have any comments on this patch set
> > > > > > >
> > > > > >
> > > > > > HI Jagadeesh,
> > > > > >
> > > > > > What does RdE1Edge or RdN1Edge mean?
> > > > >
> > > > > RdE1Edge/RdN1Edge are new product name
> > > > > Rd stands for reference design.
> > > > >
> > > > > The Neoverse E1 Edge Reference Design
> > > > > The Neoverse N1 Edge Reference Design
> > > > >
> > > >
> > > > So 'reference design' is the name of the platform based on the
> > > > Neoverse E1 and N1, respectively?
> > >
> > > yes ,
> > > 'reference design' is a class of platform, in which we have Neoverse
> > > E1/N1 cores support. Going forward other cores can come in
> > >
> >
> > Could we drop the 'edge'? It seems redundant.
>
> Hi Ard,
>
> 'edge' here would be required because there is also a 'hyperscale'
> class of platform based on N1 cores.
> (https://www.anandtech.com/show/13959/arm-announces-neoverse-n1-platform/3).
>
> >
> > I'd prefer it if we could stick with
> >
> > NeoverseE1
> > NeoverseN1
> >
> > or if the reference design part is relevant
> >
> > NeoverseE1ReferenceDesign
> > NeoverseN1ReferenceDesign
>
> The ReferenceDesign part is relevant and without which the name would
> only indicate the CPU name (NeoverseN1). And so is 'edge' because
> there is 'hyperscale' variant as of today and there could be other
> variants as well.
>

Hi Thomas,

Thanks for the clarification.

So could we go with

> > NeoverseE1EdgeReferenceDesign
> > NeoverseN1EdgeReferenceDesign

instead?


  reply	other threads:[~2019-03-15 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  6:41 [PATCH edk2-platforms 0/2] Platforms/ARM/SgiPkg: apply product names for sgiclarka and sgiclarkh platforms Jagadeesh Ujja
2019-03-05  6:41 ` [PATCH edk2-platforms 1/2] Platforms/ARM/SgiPkg: Rename SgiClarkAres to RdN1Edge Jagadeesh Ujja
2019-03-05  6:41 ` [PATCH edk2-platforms 2/2] Platforms/ARM/SgiPkg: Rename SgiClarkHelios to RdE1Edge Jagadeesh Ujja
2019-03-13  8:48 ` [PATCH edk2-platforms 0/2] Platforms/ARM/SgiPkg: apply product names for sgiclarka and sgiclarkh platforms Jagadeesh Ujja
2019-03-15  8:21   ` Jagadeesh Ujja
2019-03-15 10:44     ` Ard Biesheuvel
2019-03-15 11:16       ` Jagadeesh Ujja
2019-03-15 11:18         ` Ard Biesheuvel
2019-03-15 11:40           ` Jagadeesh Ujja
2019-03-15 11:57             ` Ard Biesheuvel
2019-03-15 12:25               ` Thomas Abraham
2019-03-15 12:29                 ` Ard Biesheuvel [this message]
2019-03-15 12:44                   ` Thomas Abraham
2019-03-15 12:50                     ` Ard Biesheuvel
2019-03-15 13:06                       ` Thomas Abraham

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-list 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=CAKv+Gu8z6-YVhYu5x5GyG3-_RuU_Dw8uJnn9khp5Ai5tQ6QcBg@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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