From: Divy Le Ray <divy@chelsio.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: netdev@vger.kernel.org, general@lists.openfabrics.org,
jeff@garzik.org, linux-kernel@vger.kernel.org
Subject: [ofa-general] Re: [PATCH 2.6.22 5/5] iw_cxgb3: Update required firmware revision to 4.0.0.
Date: Fri, 27 Apr 2007 09:52:55 -0700 [thread overview]
Message-ID: <46322A67.5070608@chelsio.com> (raw)
In-Reply-To: <adaps5qo6hh.fsf@cisco.com>
Roland Dreier wrote:
> > Update required firmware revision to 4.0.0.
>
> Hmm... should we fold this into the earlier patch, which actually
> needs this new FW? Or at least merge this patch first?
>
> Also, is it cool with everyone to require a new FW, even for users who
> might not be using (or even building) the RDMA driver? I'm not sure
> what a good solution would be really, so maybe the pain of forcing
> everyone to update FW is the least bad thing to do.
>
>
Hi Roland,
The FW update required code changes in the RDMA driver, so Steve took
care of submitting the update patch.
The new FW is required for the NIC driver too.
Cheers,
Divy
next prev parent reply other threads:[~2007-04-27 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 20:20 [ofa-general] [PATCH 2.6.22 0/5] iw_cxgb3: Bug Fixes + Firmware update Steve Wise
2007-04-26 20:21 ` [ofa-general] [PATCH 2.6.22 1/5] iw_cxgb3: Fix TERM codes Steve Wise
2007-04-26 20:21 ` [ofa-general] [PATCH 2.6.22 2/5] iw_cxgb3: Fail qp creation if the requested max_inline is too large Steve Wise
2007-04-26 20:21 ` [ofa-general] [PATCH 2.6.22 3/5] iw_cxgb3: Initialize cpu_idx field in cpl_close_listserv_req message Steve Wise
2007-04-26 20:21 ` [ofa-general] [PATCH 2.6.22 4/5] iw_cxgb3: Support for new abort logic Steve Wise
2007-04-26 20:21 ` [ofa-general] [PATCH 2.6.22 5/5] iw_cxgb3: Update required firmware revision to 4.0.0 Steve Wise
2007-04-27 3:12 ` [ofa-general] " Roland Dreier
2007-04-27 13:03 ` Steve Wise
2007-04-27 16:52 ` Divy Le Ray [this message]
2007-04-30 23:59 ` [ofa-general] " Roland Dreier
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=46322A67.5070608@chelsio.com \
--to=divy@chelsio.com \
--cc=general@lists.openfabrics.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.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).