[RFC] Patch to Abstract Ethernet PHY support (using driver model)

Andy Fleming afleming at freescale.com
Fri Dec 24 08:00:13 EST 2004

It has been suggested that I split the patch into 2 parts: gianfar 
specific stuff, and PHY specific stuff.

Here is the result:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfar_12232004.patch
Type: application/octet-stream
Size: 79067 bytes
Desc: not available
Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20041223/18921bca/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phy_12232004.patch
Type: application/octet-stream
Size: 75453 bytes
Desc: not available
Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20041223/18921bca/attachment-0001.obj 
-------------- next part --------------

On Dec 23, 2004, at 13:01, Andy Fleming wrote:

> Adds a Phy Abstraction Layer which allows ethernet controllers to 
> manage their PHYs without knowing the details of how the particular 
> PHY device operates.  This code steals heavily from BenH's  sungem 
> driver, and got some stuff out of Jason McMullan's patch.
> Primary features of the code:
> * Allows drivers to only use what they want (to a degree).  If you 
> want to handle it all yourself, but use some of the data structures 
> and functions, that's ok.  If you want to handle your own interrupts, 
> that's fine.  However, it also allows you to minimize PHY management 
> code.  See the gianfar driver patches (included for reference).
> * Integrates with current ethtool/mii defined fields.
> * Uses the driver model to manage binding PHY drivers to PHY devices, 
> and MDIO bus drivers to MDIO bus devices.
> * Doesn't affect drivers which don't use it.

More information about the Linuxppc-embedded mailing list