From: Ben Hutchings <ben@decadent.org.uk>
To: Eilon Greenstein <eilong@broadcom.com>,
Dmitry Kravkov <dmitry@broadcom.com>,
Vladislav Zolotarov <vladz@broadcom.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: bnx2x firmware version 6.x.y
Date: Sat, 17 Dec 2011 16:52:26 +0000 [thread overview]
Message-ID: <1324140746.2825.335.camel@deadeye> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
In general, linux-firmware includes all blobs that any released version
of a driver may need.
Therefore, I'm about to add the bnx2x firmware versions 6.0.34.0,
6.2.5.0 and 6.2.9.0 (taken from kernel versions 2.6.37, 2.6.38 and 3.0
respectively) into linux-firmware.
The full lists of bnx2x firmware blobs that will be included after this
is:
bnx2x-e1-4.8.53.0.fw
bnx2x-e1-5.2.13.0.fw
bnx2x-e1-5.2.7.0.fw
bnx2x-e1h-4.8.53.0.fw
bnx2x-e1h-5.2.13.0.fw
bnx2x-e1h-5.2.7.0.fw
bnx2x/bnx2x-e1-6.0.34.0.fw
bnx2x/bnx2x-e1-6.2.5.0.fw
bnx2x/bnx2x-e1-6.2.9.0.fw
bnx2x/bnx2x-e1-7.0.20.0.fw
bnx2x/bnx2x-e1-7.0.23.0.fw
bnx2x/bnx2x-e1-7.0.29.0.fw
bnx2x/bnx2x-e1h-6.0.34.0.fw
bnx2x/bnx2x-e1h-6.2.5.0.fw
bnx2x/bnx2x-e1h-6.2.9.0.fw
bnx2x/bnx2x-e1h-7.0.20.0.fw
bnx2x/bnx2x-e1h-7.0.23.0.fw
bnx2x/bnx2x-e1h-7.0.29.0.fw
bnx2x/bnx2x-e2-6.0.34.0.fw
bnx2x/bnx2x-e2-6.2.5.0.fw
bnx2x/bnx2x-e2-6.2.9.0.fw
bnx2x/bnx2x-e2-7.0.20.0.fw
bnx2x/bnx2x-e2-7.0.23.0.fw
bnx2x/bnx2x-e2-7.0.29.0.fw
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2011-12-17 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 16:52 Ben Hutchings [this message]
2011-12-18 9:21 ` bnx2x firmware version 6.x.y Eilon Greenstein
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=1324140746.2825.335.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=dmitry@broadcom.com \
--cc=dwmw2@infradead.org \
--cc=eilong@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladz@broadcom.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