| 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
| ||
|
Message-ID: <20141117160038.GB14630@localhost> Date: Mon, 17 Nov 2014 17:00:38 +0100 From: Johan Hovold <johan@...nel.org> To: Bruno Thomsen <bth@...strup.dk> Cc: Johan Hovold <johan@...nel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "f.fainelli@...il.com" <f.fainelli@...il.com>, "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>, "bruno.thomsen@...il.com" <bruno.thomsen@...il.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: phy/micrel: KSZ8031RNL RMII clock reconfiguration bug On Mon, Nov 17, 2014 at 02:56:45PM +0000, Bruno Thomsen wrote: > > Did you specify a led-mode as well, or was the Operation Mode Strap > > Override (OMSO) write the first access after the soft reset? > > No led-mode was specified so OMSO was the first write. Did you try setting a led-mode before changing the clock mode? Perhaps that could also trigger the problem (i.e. when the clock-mode change isn't the first write after reset). > > Would you able to test my series on your setup, and possibly a > > couple of diagnostic patches on top? > > Sure, I can try later this week. Much appreciated. I'll resend the last part of the series (which is not already in linux-next) and make sure to put you on CC. Thanks, Johan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists