BNX2 MIPS06 firmware in tree is 6.2.1, driver wants 6.2.3
Subsystems (2)
-----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: [email protected]
-----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-----
Quoted 15 lines · Tony Vroon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Good morning,
As of mainline commit
c2c20ef43d00b1439631e603f8dcee9a803cd8b3in December 2011, the BNX2 driver requests bnx2/bnx2-mips-06-6.2.3.fw; however thefirmware/bnx2directory 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.
Quoted 4 lines
Would it be possible to get back to this situation by updating the relevant
firmware/bnx2files 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.
You're supposed to upgrade firmware blobs on your own.
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=summary
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 1 line · Eric Dumazet
You're supposed to upgrade firmware blobs on your own.
But the firmware is in the kernel tree still, should the outdated files be removed?
Regards,
- --
Tony Vroon
Server systems manager
London Internet Exchange Ltd, Trinity Court, Trinity Street, Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: [email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/ytkoACgkQp5vW4rUFj5rN6QCfRdG1iTExVUUp6W3LPQ0Cqt/P VJEAoIaPAAXSm5qRFeC/e6keQyqzPUYS
=JmDu
-----END PGP SIGNATURE-----
Quoted 8 lines · Tony Vroon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 1 line · Eric Dumazet
You're supposed to upgrade firmware blobs on your own.
But the firmware is in the kernel tree still, should the outdated files be removed?
I believe firmware/README.AddingFirmware contains the rationale.