DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 417] CentOS7/RHEL7 nasm version too old for intel-ipsec-mb
Date: Wed, 04 Mar 2020 11:52:36 +0000	[thread overview]
Message-ID: <bug-417-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=417

            Bug ID: 417
           Summary: CentOS7/RHEL7 nasm version too old for intel-ipsec-mb
           Product: DPDK
           Version: 20.02
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: kevuzaj@gmail.com
  Target Milestone: ---

Some crypto drivers like KASUMI/SNOW 3G/ZUC require intel-ipsec-mb. However, on
CentOS7/RHEL7 with the default repos, the nasm version is too old for
intel-ipsec-mb.

Not sure if these drivers are intended to work on CentOS7/RHEL7. If not, it
would be good to update the documentation.

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.7 (Maipo)

# rpm -qa | grep nasm
nasm-2.10.07-7.el7.x86_64

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-03-04 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-417-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).