linux-kernel - Re: bnx2: broken firware loading

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 11 Nov 2016 08:44:31 -0500 (EST)
From:   Jay Rouman <jsr@....edzone.net>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
CC:     Baoquan He <bhe@...hat.com>, Frank Reppin <frank@...ermydesk.org>,
        linux-kernel@...r.kernel.org, jroedel@...e.de
Subject: Re: bnx2: broken firware loading

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@...one.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