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] [day] [month] [year] [list]
Message-ID: <2e1aa979be713dc6c84e382b12ffe43344856933.camel@mellanox.com>
Date:   Thu, 25 Jul 2019 20:56:10 +0000
From:   Saeed Mahameed <saeedm@...lanox.com>
To:     "skalluru@...vell.com" <skalluru@...vell.com>,
        "davem@...emloft.net" <davem@...emloft.net>
CC:     "aelior@...vell.com" <aelior@...vell.com>,
        "mkalderon@...vell.com" <mkalderon@...vell.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 2/2] qed: Add API for flashing the nvm
 attributes.

On Thu, 2019-07-25 at 00:48 +0000, Sudarsana Reddy Kalluru wrote:
> > > 
> > -----Original Message-----
> > From: Saeed Mahameed <saeedm@...lanox.com>
> > Sent: Thursday, July 25, 2019 1:13 AM
> > To: Sudarsana Reddy Kalluru <skalluru@...vell.com>;
> > davem@...emloft.net
> > Cc: Ariel Elior <aelior@...vell.com>; Michal Kalderon
> > <mkalderon@...vell.com>; netdev@...r.kernel.org
> > Subject: [EXT] Re: [PATCH net-next 2/2] qed: Add API for flashing
> > the nvm
> > attributes.
> > 
> > External Email
> > 
> > -----------------------------------------------------------------
> > -----
> > On Tue, 2019-07-23 at 21:51 -0700, Sudarsana Reddy Kalluru wrote:
> > > The patch adds driver interface for reading the NVM config
> > > request and
> > > update the attributes on nvm config flash partition.
> > > 
> > 
> > You didn't not use the get_cfg API you added in previous patch.
> Thanks for your review. Will move this API to the next patch series
> which will plan to send shortly.
> 
> > Also can you please clarify how the user reads/write from/to NVM
> > config
> > ? i mean what UAPIs and tools are being used ?
> NVM config/partition will be updated using ethtool flash update
> command (i.e., ethtool -f) just like the update of 
> other flash partitions of qed device. Example code path,
>   ethool-flash_device --> qede_flash_device() --> qed_nvm_flash() --> 
> qed_nvm_flash_cfg_write()
> 

I see, thanks for the clarification.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ