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] [day] [month] [year] [list]
Message-Id: <20130531.172732.1438540273906277034.davem@davemloft.net>
Date:	Fri, 31 May 2013 17:27:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	vipul@...lsio.com
Cc:	netdev@...r.kernel.org, divy@...lsio.com, dm@...lsio.com,
	jay@...lsio.com
Subject: Re: [PATCH net-next] cxgb4: Force uninitialized state if
 FW_ON_ADAPTER is < FW_VERSION and we're the MASTER_PF

From: Vipul Pandya <vipul@...lsio.com>
Date: Thu, 30 May 2013 18:54:14 +0530

> From: Jay Hernandez <jay@...lsio.com>
> 
> Forcing uninitialized state allows us to upgrade and reinitialize the adapter.
> 
> FW_VERSION_T4 = 1.4.0.0
> FW_VERSION_T5 = 0.0.0.0
> At this point driver supports above and greater than above version of firmware.
> If it doesn't find the required firmware version than it forces the adapter to
> be reinitialized as shown below.
> 
> 1) If FW_ON_ADAPTER < FW_VERSION and we're the MASTER_PF force uninitialized
>    state and a FW upgrade if available.
> 
>        - If FW_ON_ADAPTER < /lib/firmware/cxgb4/t*fw.bin we will update the
>          adapters FW.
>        - If FW_ON_ADAPTER >= /lib/firmware/cxgb4/t*fw.bin don't upgrade FW.
>        - If upgrade_fw() fails force reinitialization of the adapter anyways,
>          it might still work.
> 
>    Either way forcing the uninitialized state allows cxgb4 reinitialize FW.
> 
> 2) If FW_ON_ADAPTER >= FW_VERSION driver follows normal path.
> 
> Signed-off-by: Jay Hernandez <jay@...lsio.com>

Applied.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ