From: Tony Vroon <tony@linx.net>
To: Michael Chan <mchan@broadcom.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Anthony G. Basile" <basile@virtual.dyc.edu>
Subject: BNX2 MIPS06 firmware in tree is 6.2.1, driver wants 6.2.3
Date: Tue, 03 Jul 2012 09:50:43 +0100 [thread overview]
Message-ID: <4FF2B263.4080000@linx.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good morning,
As of mainline commit c2c20ef43d00b1439631e603f8dcee9a803cd8b3 in
December 2011, the BNX2 driver requests bnx2/bnx2-mips-06-6.2.3.fw;
however the firmware/bnx2 directory in the kernel sources only
contains bnx2/bnx2-mips-06-6.2.1.fw so the call fails.
The network interfaces will not come up at all, making it necessary to
steal & rename 6.2.1 firmware to get the interfaces up, and then
install a linux-firmware tarball. Before this commit, the bnx2 driver
as compiled was self-sufficient.
Would it be possible to get back to this situation by updating the
relevant firmware/bnx2 files in the kernel sources please? I noticed
this problem in an upgrade from 3.2.11 to 3.4.2, but I verified it is
still an issue in mainline today.
Regards,
- --
Tony Vroon
Server systems manager
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/ysmMACgkQp5vW4rUFj5oIpQCcClnaGH3ZTEGfqOuDCQ05wxUD
43cAoL6KJH8zmbY+UQoGedriKbcdnrbh
=3wGg
-----END PGP SIGNATURE-----
next reply other threads:[~2012-07-03 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 8:50 Tony Vroon [this message]
2012-07-03 9:05 ` BNX2 MIPS06 firmware in tree is 6.2.1, driver wants 6.2.3 Eric Dumazet
2012-07-03 9:07 ` Tony Vroon
2012-07-03 9:30 ` Eric Dumazet
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=4FF2B263.4080000@linx.net \
--to=tony@linx.net \
--cc=basile@virtual.dyc.edu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-netdev@vger.kernel.org \
--cc=mchan@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 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.