From: Jay Rouman <jsr@dex.edzone.net>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Baoquan He <bhe@redhat.com>, Frank Reppin <frank@undermydesk.org>,
linux-kernel@vger.kernel.org, jroedel@suse.de
Subject: Re: bnx2: broken firware loading
Date: Fri, 11 Nov 2016 08:44:31 -0500 (EST) [thread overview]
Message-ID: <E1c5C87-0006XG-C2@dex.edzone.net> (raw)
In-Reply-To: <560a68b9-bc73-9d53-ab95-35cd5cb9504d@molgen.mpg.de>
The part that confuses me is that the kernels that I use are custom
configured for a particular machine. I don't use initramfs or even
allow module loading. All the drivers are actually in the kernel. As
far as I know, no firmware is loaded. But the regression stops the BNX2
NIC from being discovered by the kernel. Does this make sense? It
seems like removing the firmware loading stops the discovery process
even though no firmware is actually loaded either way.
--
Jay Rouman (jsr@edzone.net)
Gratiot/Isabella RESD, Ithaca, MI
> On 11/10/16 19:19, Jay Rouman wrote:
> > Did this get pushed upstream? I see a new patch for 4.8.7 but the BNX2
> > regression doesn't seem to be fixed. Or am I missing something?
>
> I don?t think Baoquan?s patch is ready yet.
>
> I guess he will put you in the receivers list, once he sends it for review.
>
> As a workaround, you can put the firmware in the initramfs.
>
>
> Kind regards,
>
> Paul
next prev parent reply other threads:[~2016-11-11 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 22:50 bnx2: broken firware loading Frank Reppin
2016-11-09 0:19 ` Baoquan He
2016-11-10 18:19 ` Jay Rouman
2016-11-11 12:52 ` Paul Menzel
2016-11-11 13:44 ` Jay Rouman [this message]
2016-11-11 13:50 ` Baoquan He
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=E1c5C87-0006XG-C2@dex.edzone.net \
--to=jsr@dex.edzone.net \
--cc=bhe@redhat.com \
--cc=frank@undermydesk.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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).