DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Herbert Guan <herbert.guan@arm.com>,
	Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com
Subject: Re: [dpdk-dev] [PATCH v1] build: add more implementers' IDs and PNs for Arm platforms
Date: Thu, 1 Feb 2018 14:35:15 +0000	[thread overview]
Message-ID: <20180201143514.GA6620@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <1517384359-1438-1-git-send-email-herbert.guan@arm.com>

On Wed, Jan 31, 2018 at 03:39:19PM +0800, Herbert Guan wrote:
> 1) Add native PN option '-march=native' to allow automatic detection.
>    Set 'arm_force_native_march' to 'true' in config/arm/meson.build
>    to use native PN option.
> 2) Add implementer_pn option for part num selection in cross compile
> 3) Add known Arm cortex PN support
> 4) Add known implementers' IDs (use generic flags/archs by default)
> 5) Sync build options with config/common_armv8a_linuxapp
> 
> Signed-off-by: Herbert Guan <herbert.guan@arm.com>
> ---

Is it intended to get this into 18.02, or can it be delayed till 18.05? 

Pavan, can you please review, as author of the existing ARM-specific
meson code?

Thanks,
/Bruce

  reply	other threads:[~2018-02-01 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  5:12 [dpdk-dev] [PATCH] " Herbert Guan
2018-01-31  7:39 ` [dpdk-dev] [PATCH v1] " Herbert Guan
2018-02-01 14:35   ` Bruce Richardson [this message]
2018-02-05  9:22   ` Pavan Nikhilesh
2018-02-06  5:51     ` Herbert Guan
2018-02-06  6:02       ` Pavan Nikhilesh
2018-02-06 15:12         ` Bruce Richardson

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=20180201143514.GA6620@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=herbert.guan@arm.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=pbhagavatula@caviumnetworks.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 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).