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
| ||
|
Date: Wed, 16 Nov 2016 00:03:17 +0100 From: Andrew Lunn <andrew@...n.ch> To: Lino Sanfilippo <LinoSanfilippo@....de> Cc: Florian Fainelli <f.fainelli@...il.com>, davem@...emloft.net, charrer@...critech.com, liodot@...il.com, gregkh@...uxfoundation.org, devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver > >>>>> + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG | > >>>>> + SLIC_PCR_AUTONEG_RST; > >>>>> + slic_write(sdev, SLIC_REG_WPHY, val); > Thats essentially what I meant by setting a flag in the irq handler. The mdio > function would have to check somehow if the irq has been fired (be it by means > of a flag or a completion that is set by the irq handler and checked by the > mdio function). So I agree that it should work (if reading via the AP command > is actually possible). It seems odd you have a nice simple way to do writes, but reads are very complex. There might be a simple read method hiding somewhere. Andrew
Powered by blists - more mailing lists