From: Aws Ismail <aws.ismail@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] support for X552/X557-AT 10GBase-T devices
Date: Fri, 13 Nov 2015 13:13:37 -0500 [thread overview]
Message-ID: <CAMHMu0MgYrqjCQ2s5mtLopdsJCUwKJ6u_bvxbSPKPBg2vqHy8A@mail.gmail.com> (raw)
In-Reply-To: <2584503.Vl16qpNLEm@xps13>
On Fri, Nov 13, 2015 at 11:40 AM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> 2015-11-13 11:32, Aws Ismail:
>> I just wanted to confirm whether the 0x15ad X552/X557-AT 10GBase-T
>> devices are currently "fully" supported by DPDK (master).
>
> My understanding is that it is supported:
> http://dpdk.org/browse/dpdk/commit/?id=2e83c81bad
> (but you can have a hint in the last letters of the commit id ;)
>
Thanks Thomas for the reply,
:) I would agree on that. It seems to me support is just experimental for now.
>> I have looked at the ixgbe PMD code and I can see 0x15AD being
>> mentioned in the device list but I am unable to fully use it even with
>> the testpmd app.
>
> So I think you can send a bug report on this list.
Is there a process to file a bug? on the dev page
(http://dpdk.org/dev) there is no mention about how to send in a bug
report. Is there a bugzilla page for DPDK somewhere?
>
>> I understand that the 0x15ad devices are not yet fully supported in
>> the mainline kernel (even in 4.3.x) as of yet, but I wonder if the PMD
>> usually lags behind the mainline driver.
>
> There is no rule and really often they are not written by the same developpers.
next prev parent reply other threads:[~2015-11-13 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 16:32 Aws Ismail
2015-11-13 16:40 ` Thomas Monjalon
2015-11-13 18:13 ` Aws Ismail [this message]
2015-11-13 20:33 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2015-11-10 21:08 Aws Ismail
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=CAMHMu0MgYrqjCQ2s5mtLopdsJCUwKJ6u_bvxbSPKPBg2vqHy8A@mail.gmail.com \
--to=aws.ismail@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).