netdev - Re: Generic PHY lib vs. locking

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]

Message-id: <1166801090.30347.1.camel@dhollis-lnx.sunera.com>
Date:	Fri, 22 Dec 2006 10:24:50 -0500
From:	David Hollis <dhollis@...ehollis.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Andy Fleming <afleming@...escale.com>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: Generic PHY lib vs. locking

On Fri, 2006-12-22 at 15:07 +1100, Benjamin Herrenschmidt wrote:
> Hi Andy !
> 
> I've been looking at porting various drivers (EMAC, sungem,
> spider_net, ...) to the generic PHY stuff. However, I have one
> significant problem here.
> 

> One solution would be to change it to use a mutex instead of a lock as
> well, though that would change the requirements of where phy_start/stop
> can be called, and use a delayed work queue instead of a timer.

Wouldn't this change also allow it to be used with USB Ethernet devices?
I was looking at porting the asix.c drive to use the PHY layer but the
locking killed that effort since USB devices can't do spinlocks without
hosing things up.

-- 
David Hollis <dhollis@...ehollis.com>

-
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