From: "Magnos A. Hammes" <magnos@taghos.com.br>
To: Michael Chan <mchan@broadcom.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] drivers/net/ethernet/broadcom/bnx2.c
Date: Thu, 01 May 2014 13:36:36 -0300 [thread overview]
Message-ID: <53627814.7090106@taghos.com.br> (raw)
In-Reply-To: <1398922768.3056.4.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
On 01-05-2014 02:39, Michael Chan wrote:
> On Thu, 2014-05-01 at 00:42 -0300, Magnos A. Hammes wrote:
>> Hello,
>>
>>
>> I have a Dell server with the following Broadcom gigabit network
>> adapter that uses the bnx2 driver:
>>
>> 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II
>> BCM5716 Gigabit Ethernet (rev 20)
>>
>> I was using kernel 3.2.57 and 3.13.3, but in both of them I faced some
>> trouble to make the ethernet adapter work, whatever version of this
>> two kernels that I try to boot I get the same error:
>>
>> Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"
>> Direct firmware load failed with error -2
>>
> We no longer put the firmware in the kernel tree, so you need to
> download the firmware from the linux-firmware git tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
>
>
>
Ok, I cloned that git tree and used the firmwares available there, but
it didn't work with this firmware: bnx2/bnx2-mips-09-6.2.1b.fw sha1sum
8f11b39a60a4e1dd3774a10218c913f1cb761353
It only works when I change the source code of
"drivers/net/ethernet/broadcom/bnx2.c" and compile the kernel again,
making him load this firmware "bnx2/bnx2-mips-09-6.2.1a.fw" instead of
"bnx2/bnx2-mips-09-6.2.1b.fw".
Magnos A. Hammes
next prev parent reply other threads:[~2014-05-01 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5361C29C.5060808@taghos.com.br>
2014-05-01 5:39 ` [PATCH] drivers/net/ethernet/broadcom/bnx2.c Michael Chan
2014-05-01 16:36 ` Magnos A. Hammes [this message]
2014-05-01 17:39 ` Michael Chan
2014-05-01 18:49 ` Magnos A. Hammes
2014-05-01 19:32 ` Michael Chan
2014-05-02 16:26 ` Ben Hutchings
2014-05-02 18:27 ` Magnos A. Hammes
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=53627814.7090106@taghos.com.br \
--to=magnos@taghos.com.br \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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.