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, 3 Jun 2021 17:54:31 +0000
From:   Liang Xu <lxu@...linear.com>
To:     Andrew Lunn <andrew@...n.ch>
CC:     "Russell King (Oracle)" <linux@...linux.org.uk>,
        "hkallweit1@...il.com" <hkallweit1@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "vee.khee.wong@...ux.intel.com" <vee.khee.wong@...ux.intel.com>,
        Hauke Mehrtens <hmehrtens@...linear.com>,
        Thomas Mohren <tmohren@...linear.com>
Subject: Re: [PATCH v2] net: phy: add Maxlinear GPY115/21x/24x driver

On 4/6/2021 1:05 am, Andrew Lunn wrote:
> This email was sent from outside of MaxLinear.
>
>
>> The firmware version can change because of switch of the firmware during
>> running time.
> Please could you explain this some more. What happens if i initialize
> the PHY and then it decided to switch its firmware. Is the
> configuration kept? Does it need reconfiguring?
>
>        Andrew
>
In one of our product (in developing), the NIC driver can decide to 
switch to 2nd firmware.

The switch happens when network interface is down.

After the switch, when the network interface is up, phy_init_hw is 
triggered to init the phy.

The PHY device itself won't decide to switch firmware.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ