DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2] config/arm: add Qualcomm Centriq 2400 part number
Date: Thu, 17 Jun 2021 07:28:10 +0000	[thread overview]
Message-ID: <AM5PR0802MB24656CB7E1BAF8FD154082649E0E9@AM5PR0802MB2465.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <2543587.JZCs38hApF@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, June 17, 2021 3:07 PM
> To: jerinj@marvell.com; Ruifeng Wang <Ruifeng.Wang@arm.com>;
> Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Cc: dev@dpdk.org; Thierry Herbelot <thierry.herbelot@6wind.com>; Juraj
> Linkeš <juraj.linkes@pantheon.tech>
> Subject: Re: [dpdk-dev] [PATCH v2] config/arm: add Qualcomm Centriq 2400
> part number
> 
> 25/05/2021 10:24, Thierry Herbelot:
> > 0xc00 is for "SoC 2.0" Qualcom Centriq servers.
> > 0x800 is for "SoC 1.1".
> >
> > Cc: Jerin Jacob <jerinj@marvell.com>
> > Cc: Ruifeng Wang <ruifeng.wang@arm.com>
> > Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> > Cc: Juraj Linkeš <juraj.linkes@pantheon.tech>
> >
> > Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> > --
> > V2: add maintainers as Cc
> > ---
> > --- a/config/arm/meson.build
> > +++ b/config/arm/meson.build
> > @@ -226,6 +226,7 @@ soc_bluefield = {
> >  soc_centriq2400 = {
> >      'description': 'Qualcomm Centriq 2400',
> >      'implementer': '0x51',
> > +    'part_number': '0x800',
To add support for a new part number, I think it should be added to implementer_qualcomm.
If cross compile for the new soc is needed, it needs a new soc_xx block. I'm wondering this is a real request? I assume SoC 1.0 will have no config difference from SoC 2.0.

Thanks.
> >      'part_number': '0xc00',
> >      'numa': false
> >  }
> 
> Any comment or ack?
> 


  parent reply	other threads:[~2021-06-17  7:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  8:16 [dpdk-dev] [PATCH] " Thierry Herbelot
2021-05-25  8:18 ` Thomas Monjalon
2021-05-25  8:24 ` [dpdk-dev] [PATCH v2] " Thierry Herbelot
2021-06-17  7:06   ` Thomas Monjalon
2021-06-17  7:21     ` David Marchand
2021-06-17  7:24     ` Ruifeng Wang
2021-06-17  7:28     ` Ruifeng Wang [this message]
2021-06-17  8:16   ` [dpdk-dev] [PATCH V3] " Thierry Herbelot
2021-06-17 10:03     ` Ruifeng Wang
2021-06-17 11:24       ` Thierry Herbelot
2021-06-17 14:46         ` Ruifeng Wang
2021-06-17 11:36     ` [dpdk-dev] [PATCH V4] " Thierry Herbelot
2021-06-17 11:44       ` [dpdk-dev] [PATCH V5] " Thierry Herbelot
2021-06-17 15:13         ` [dpdk-dev] [PATCH V6] " Thierry Herbelot
2021-06-18  2:09           ` Ruifeng Wang
2021-06-18  8:51             ` Thomas Monjalon
2021-06-18  8:53               ` Thierry Herbelot
2021-06-18  8:58                 ` Thomas Monjalon
2021-06-21  1:52                   ` Ruifeng Wang
2021-07-09 15:27                     ` Thomas Monjalon

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=AM5PR0802MB24656CB7E1BAF8FD154082649E0E9@AM5PR0802MB2465.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=nd@arm.com \
    --cc=thierry.herbelot@6wind.com \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).