From: Baoquan He <bhe@redhat.com>
To: Jay Rouman <jsr@dex.edzone.net>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Frank Reppin <frank@undermydesk.org>,
linux-kernel@vger.kernel.org, jroedel@suse.de
Subject: Re: bnx2: broken firware loading
Date: Fri, 11 Nov 2016 21:50:09 +0800 [thread overview]
Message-ID: <20161111135009.GC15325@x1> (raw)
In-Reply-To: <E1c5C87-0006XG-C2@dex.edzone.net>
On 11/11/16 at 08:44am, Jay Rouman wrote:
> 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.
I tried but didn't find a bnx2 chip spec. Now I post a patches to revert
my previous commit and add a function to only try to hard reset bnx2
chip but not involving firmware issues.
Will wait and see what bnx2 experts will say.
Sorry about the thouble I made to you.
> --
> 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
prev parent reply other threads:[~2016-11-11 13:50 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
2016-11-11 13:50 ` Baoquan He [this message]
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=20161111135009.GC15325@x1 \
--to=bhe@redhat.com \
--cc=frank@undermydesk.org \
--cc=jroedel@suse.de \
--cc=jsr@dex.edzone.net \
--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 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.