netdev - Re: [PATCH net-next 0/3] net: phy: broken turn-around support

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 May 2015 22:43:26 +0200
From:	Bert Vermeulen <bert@...t.com>
To:	Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org
CC:	davem@...emloft.net, jogo@...nwrt.org
Subject: Re: [PATCH net-next 0/3] net: phy: broken turn-around support

On 05/12/2015 07:33 PM, Florian Fainelli wrote:
> Hi all,
> 
> This is an attempt at solving the broken turn-around problem in a way that
> is not specific to the mdio-gpio driver, since it affects different kinds of
> platforms.
> 
> We cannot make that localized to PHY device drivers because probing the PHY
> device which has a broken turn-around can fail as early as in get_phy_id(),
> therefore we need a bit of help from Device Tree/platform_data.

That is indeed a better place to put that ignore-ta flag, and the device
tree support is of course a big improvement over the previous patch as well.

But it's still too big a hammer to hit the AR8316 problem with, I think.
Just like the previous patch, this disables checking TA on _all_ reads, but
I really only need it disabled on the first read.

Are you saying you've seen other systems with this TA problem? Did those
have problems after more than just the first read?

-- 
Bert Vermeulen        bert@...t.com          email/xmpp
--
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