netdev - Re: [PATCH net-next] cxgb4: continue in debug mode, if probe fails

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:	Thu, 27 Aug 2015 16:14:34 -0300
From:	Thadeu Lima de Souza Cascardo <cascardo@...hat.com>
To:	Hariprasad Shenai <hariprasad@...lsio.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net, leedom@...lsio.com,
	nirranjan@...lsio.com
Subject: Re: [PATCH net-next] cxgb4: continue in debug mode, if probe fails

On Wed, Aug 26, 2015 at 10:30:35PM +0530, Hariprasad Shenai wrote:
> If adapter is flashed with incorrect firmware, probe can fail.
> If probe fails, continue in debug mode, so one can also use the debug
> interface to update the firmware via ethtool.
> 
> Signed-off-by: Hariprasad Shenai <hariprasad@...lsio.com>

What do you mean by incorrect firmware? I know the driver can cope with older
firmware if force_old_init is used, for example. Isn't it possible to detect
those old firmware versions and do the same as force_old_init does?

Cascardo.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html