From: "Jan Remeš" <remes@netcope.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
bruce.richardson@intel.com,
Rastislav Cernay <cernay@netcope.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] use pkg-config to find Netcope dependencies
Date: Mon, 16 Sep 2019 18:52:36 +0200 [thread overview]
Message-ID: <CAAnEdtDsmty6DqNRK933A0ckZCsNfA3cr9vUvdqBPY6dswhWYQ@mail.gmail.com> (raw)
In-Reply-To: <d95c4bb1-0a5f-3f40-f402-ae341e18095c@intel.com>
On Mon, Sep 16, 2019 at 5:34 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> +1 to this patch, unrelated to this patch I remember there was an issue with the
> nfb & szedata2 dependencies, that their dependencies conflict with each other,
> so it wasn't possible to enable both at the same time.
>
> Jan, Rastislav,
>
> Is it still the case, or is there any improvement there?
They work with the same hardware, they are (crudely and rudely
speaking) just mutually incompatible versions of the same thing (both
provide configuration access and data transfer for Netcope NFB family
of FPGA cards).
Therefore, there is no motivation to install both of them, "szedata2
(libsze2)" is deprecated and we only want to keep the PMD for existing
users. If it becomes a burden, we will phase it out eventually.
Regards,
Jan
next prev parent reply other threads:[~2019-09-16 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 9:36 Thomas Monjalon
2019-09-14 9:36 ` [dpdk-dev] [PATCH 1/2] net/nfb: fix dependency check Thomas Monjalon
2019-09-15 12:04 ` Jan Remeš
2019-09-16 15:46 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-09-16 15:51 ` Thomas Monjalon
2019-09-14 9:37 ` [dpdk-dev] [PATCH 2/2] net/szedata2: " Thomas Monjalon
2019-09-15 12:05 ` Jan Remeš
2019-09-16 15:34 ` [dpdk-dev] [PATCH 0/2] use pkg-config to find Netcope dependencies Ferruh Yigit
2019-09-16 16:52 ` Jan Remeš [this message]
2019-10-03 15:23 ` Ferruh Yigit
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=CAAnEdtDsmty6DqNRK933A0ckZCsNfA3cr9vUvdqBPY6dswhWYQ@mail.gmail.com \
--to=remes@netcope.com \
--cc=bruce.richardson@intel.com \
--cc=cernay@netcope.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).