From: "Magnos A. Hammes" <magnos@taghos.com.br>
To: Michael Chan <mchan@broadcom.com>
Cc: netdev@vger.kernel.org,
"desenvolvimento@taghos.com.br" <desenvolvimento@taghos.com.br>
Subject: Re: [PATCH] drivers/net/ethernet/broadcom/bnx2.c
Date: Thu, 01 May 2014 15:49:54 -0300 [thread overview]
Message-ID: <53629752.6030606@taghos.com.br> (raw)
In-Reply-To: <1398965975.3056.40.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
On 01-05-2014 14:39, Michael Chan wrote:
> On Thu, 2014-05-01 at 13:36 -0300, Magnos A. Hammes wrote:
>> 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
>>
>
> I have the same sha1 sum on the same firmware file on my system and it
> works for me.
>
>> 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".
>
> I don't see why it wouldn't work if both firmware files are in the same
> location. May be you have some udev rules that are preventing it?
>>
>>
>
>
Yes, I have some udev rules that run at system boot, but the only thing
I do is:
/sbin/udevd --daemon
/sbin/udevadm trigger --type=subsystems --action=add
/sbin/udevadm trigger --type=devices --action=add
/sbin/udevadm settle
Udev runs normally and returns no errors or warnings and dmesg shows
nothing weird.
So, you think this may be a problem with my udev rules or a udev bug?
I'm using udev version 182.
next prev parent reply other threads:[~2014-05-01 18:50 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
2014-05-01 17:39 ` Michael Chan
2014-05-01 18:49 ` Magnos A. Hammes [this message]
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=53629752.6030606@taghos.com.br \
--to=magnos@taghos.com.br \
--cc=desenvolvimento@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox