From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756664AbcKKNop (ORCPT ); Fri, 11 Nov 2016 08:44:45 -0500 Received: from dex.edzone.net ([207.74.88.2]:36041 "EHLO dex.edzone.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756538AbcKKNoo (ORCPT ); Fri, 11 Nov 2016 08:44:44 -0500 Subject: Re: bnx2: broken firware loading In-Reply-To: <560a68b9-bc73-9d53-ab95-35cd5cb9504d@molgen.mpg.de> To: Paul Menzel Date: Fri, 11 Nov 2016 08:44:31 -0500 (EST) CC: Baoquan He , Frank Reppin , linux-kernel@vger.kernel.org, jroedel@suse.de Reply-To: jsr@dex.edzone.net X-Mailer: ELM [version 2.4ME+ PL127 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: From: Jay Rouman Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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