DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: build nfp pmd support by default
Date: Tue, 17 Jan 2017 21:55:20 +0100	[thread overview]
Message-ID: <2075524.r0YEMkGTG2@xps13> (raw)
In-Reply-To: <20170116164816.GA25960@bricha3-MOBL3.ger.corp.intel.com>

2017-01-16 16:48, Bruce Richardson:
> On Mon, Jan 16, 2017 at 04:43:11PM +0000, Ferruh Yigit wrote:
> > On 1/13/2017 11:50 AM, Alejandro Lucero wrote:
> > > Because using a NFP PMD requires specific BSP installed, the PMD
> > > support was not the default option before. This was just for making
> > > people aware of such dependency, since there is no need for such a
> > > BSP for just compiling DPDK with NFP PMD support.
> > 
> > Although NFP will compile fine, as far as I understand BSP dependency is
> > still there.
> > 
> > Thomas,
> > 
> > What do you think, is compilation enough to be enabled by default?
> > 
> > > 
> Although you haven't asked me, I think having it compiled by default is
> ok, even if you can't run it without the BSP. Having it compiled means
> that we can catch errors or problems with the driver sooner, e.g. when
> doing updates across all drivers.

+1

(I suggested this change to Alejandro if I remember well)

  parent reply	other threads:[~2017-01-17 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 11:50 Alejandro Lucero
2017-01-16 16:43 ` Ferruh Yigit
2017-01-16 16:48   ` Bruce Richardson
2017-01-16 18:21     ` Alejandro Lucero
2017-01-17 20:55     ` Thomas Monjalon [this message]
2017-01-17 23:20 ` Ferruh Yigit
2017-01-17 23:58   ` Ferruh Yigit
2017-01-18 11:13     ` Alejandro Lucero

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=2075524.r0YEMkGTG2@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).