From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Alejandro.Lucero" <alejandro.lucero@netronome.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5 8/9] nfp: adding nic guide
Date: Wed, 04 Nov 2015 16:03:48 +0100 [thread overview]
Message-ID: <2124992.NXkthnb6MB@xps13> (raw)
In-Reply-To: <1446467130-300-9-git-send-email-alejandro.lucero@netronome.com>
2015-11-02 12:25, Alejandro.Lucero:
> +Before using the Netronome's DPDK PMD some NFP-6xxx configuration,
> +which is not related to DPDK, is required. The system requires
> +installation of **Netronome's BSP (Board Support Package)** which includes
> +Linux drivers, programs and libraries.
Do you confirm we can check the PMD build without having the BSP?
next prev parent reply other threads:[~2015-11-04 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 12:25 [dpdk-dev] [PATCH v5 0/9] support for netronome nfp-6xxx card Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 1/9] nfp: basic initialization for netronome´s " Alejandro.Lucero
2015-11-04 15:05 ` Thomas Monjalon
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 2/9] nfp: rx/tx functionality Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 3/9] nfp: adding rss functionality Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 4/9] nfp: adding stats functionality Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 5/9] nfp: adding link functionality Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 6/9] nfp: adding functionality to pmd Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 7/9] nfp: integration with dpdk build system Alejandro.Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 8/9] nfp: adding nic guide Alejandro.Lucero
2015-11-04 15:03 ` Thomas Monjalon [this message]
2015-11-04 15:41 ` Alejandro Lucero
2015-11-02 12:25 ` [dpdk-dev] [PATCH v5 9/9] nfp: adding maintainers and release info 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=2124992.NXkthnb6MB@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
/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).