linux-kernel - Re: [PATCH 4/7 RESEND] cxgb3

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 for Android: free password hash cracker in your pocket

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

Message-ID: <465B5A8B.7000701@garzik.org>
Date:	Mon, 28 May 2007 18:41:15 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	divy@...lsio.com
CC:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	swise@...ngridcomputing.com
Subject: Re: [PATCH 4/7 RESEND] cxgb3 - Update FW to 4.1

divy@...lsio.com wrote:
> From: Divy Le Ray <divy@...lsio.com>
> 
> Bump FW version to 4.1.
> Modify chip tuning in consequence.
> 
> Signed-off-by: Divy Le Ray <divy@...lsio.com>
> ---
> 
>  drivers/net/cxgb3/regs.h    |    4 ++++
>  drivers/net/cxgb3/t3_hw.c   |   40 ++++++++++++++++++++++------------------
>  drivers/net/cxgb3/version.h |    2 +-
>  3 files changed, 27 insertions(+), 19 deletions(-)

You think requiring a FIRMWARE UPGRADE is something that should be done 
in the middle of a kernel bugfix series?  What Q/A planet are you from?

This is a completely ridiculous burden you are placing on the individual 
user.  A good driver knows that firmware NOT SHIPPED WITH THE KERNEL 
does not necessarily move in lock-step with the kernel driver.  You are 
welcome to GPL your firmware and ship it of course....

	Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/