From: Ben Hutchings <ben@decadent.org.uk>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: Linux NetDev <netdev@vger.kernel.org>
Subject: Re: on bnx2x firmware...
Date: Wed, 02 Nov 2011 04:36:54 +0000 [thread overview]
Message-ID: <1320208614.3079.5.camel@deadeye> (raw)
In-Reply-To: <CAHo-OowF1LNmL0P_Rt=oKmhZMt=CVaVsAYkh_XqVJEOzBPXV7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Tue, 2011-11-01 at 18:01 -0700, Maciej Żenczykowski wrote:
> ((v3.1))$ cat drivers/net/bnx2x/bnx2x_hsi.h | egrep BCM_5710_FW_
>
> #define BCM_5710_FW_MAJOR_VERSION 7
> #define BCM_5710_FW_MINOR_VERSION 0
> #define BCM_5710_FW_REVISION_VERSION 23
> #define BCM_5710_FW_ENGINEERING_VERSION 0
>
> So the desired firmware is version 7.0.23.0
>
> ((v3.1))$ find | egrep bnx2x | egrep fw
> ./firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex
> ./firmware/bnx2x/bnx2x-e2-6.2.9.0.fw.ihex
> ./firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex
> ./drivers/net/bnx2x/bnx2x_fw_defs.h
> ./drivers/net/bnx2x/bnx2x_fw_file_hdr.h
>
> So it doesn't look like the in-tree fw matches the bnx2x driver in
> released v3.1.
> I can find this firmware in the firmware repository.
[...]
That's where it belongs. But there is some confusion/disagreement on
this point.
Ben.
--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-11-02 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 1:01 on bnx2x firmware Maciej Żenczykowski
2011-11-02 4:36 ` Ben Hutchings [this message]
2011-11-03 4:36 ` Maciej Żenczykowski
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=1320208614.3079.5.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=netdev@vger.kernel.org \
--cc=zenczykowski@gmail.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).