From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
Hariprasad S <hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: [ANNOUNCE] libcxgb4-1.3.2 released.
Date: Fri, 21 Feb 2014 10:25:10 -0600 [thread overview]
Message-ID: <53077DE6.7020301@opengridcomputing.com> (raw)
The libcxgb4 package contains a userspace driver for Chelsio T4 and T5
iWARP RNICs. It is a plug-in module for libibverbs that allows programs
to use Chelsio hardware directly from userspace.
A new release is available from:
http://www.openfabrics.org/downloads/cxgb4/libcxgb4-1.3.2.tar.gz
with an md5sum of:
d6e9b98f0d58dff639662eae9866541b
The git tree is available at:
git://www.openfabrics.org/~swise/libcxgb4
The tag is v1.3.2
Shortlog from v1.3.1:
Steve Wise (16):
T4 onchip workaround: do the 16 4B MA writes just before DB ring.
Fix DEBUG code in c4iw_flush_hw_cq().
DB Drop Avoidance, Version 2.
unmap status page when freeing the context.
never consume a pending wr in sq flush.
iw_cxgb4/libcxgb4: swsq "signaled" state needs to mind sq_sig_all.
Remove dead raw qp code.
Remove dead SIM code.
Add common device id table and chip types.
Refresh t4 fw/hw reg files.
Update copyrights.
Call rmb() after reading valid gen bit.
Call wc_wmb() needed after DB writes.
Use V_PIDX_T5() for T5 devices in ring_db funcs.
Fixed compilation error with debug enabled.
Spin release 1.3.2.
reply other threads:[~2014-02-21 16:25 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=53077DE6.7020301@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.