netdev - Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx

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]

Message-ID: <35D366A0-235E-44ED-8D5B-AEDB1D8AC0F5@broadcom.com>
Date:	Tue, 14 Jun 2011 11:32:04 -0700
From:	"Vladislav Zolotarov" <vladz@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	"Michael Chan" <mchan@...adcom.com>,
	"Bhanu (Venkata Bhanu Prakash) Gollapudi" <bprakash@...adcom.com>,
	"Eilon Greenstein" <eilong@...adcom.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Dmitry Kravkov" <dmitry@...adcom.com>,
	"Yaniv Rosner" <yaniv.rosner@...adcom.com>,
	"dwmw2@...radead.org" <dwmw2@...radead.org>
Subject: Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx

On 14 ביונ 2011, at 20:47, "David Miller" <davem@...emloft.net> wrote:

> From: "Michael Chan" <mchan@...adcom.com>
> Date: Tue, 14 Jun 2011 10:35:53 -0700
> 
>> If the firmware is not integrated into net-next-2.6, the newly patched
>> driver won't work.  You get an error at run time saying the firmware is
>> not available.
>> 
>> When David Woodhouse integrates the firmware and a new firmware rpm is
>> made available for users, then the new driver will work.
> 
> This is terrible.
> 
Another option is that the person that wills to run a bisect has to start with pulling the latest linux-firmware git, copying its contents into the /lib/firmware and then start a bisect. 

This requires some sync between Dave and David: David should always be the first to integrate a new FW and only then Dave should inegrate a driver patch series with the support for this new FW. The responsibility for the ordering should be on the driver owner: in our case, i shouldn't be sending a net-next patch series until the linux-firmware patch is applied.

It doesn't sound that terrible price for having a kernel tree clean from binaries blobs... ;)

Vlad