Re: RFC: PHY Abstraction Layer II

[Glen Turner <glen.turner@xxxxxxxxxxxxx>]

Andy Fleming wrote:

> I was thinking that it would be easier for the ethernet driver to do  
> this in the adjust_link() function, since it's going to need to track  
> when these things change, anyway.  But if the general consensus is  that 
> it should be in the generic code, I can see about adding it there.
Hi Andy,

I wasn't at all saying where it should be done -- rather that
it's very useful for networking staff like myself that it is
done *somewhere*.

Without too much knowledge of the code, it would be nice if
it were done in the PHY layer, so that the messages can be
grepped for in logs. If you leave it to drivers there'll
be inconsistent levels of detail and a variety of formats.

> > Also, it would be nice to be able to retrieve PHY data
> > independent of the interface status (eg, to retrieve
> > asset serial numbers, GBIC make/models, etc).
>
> I'm not sure what you mean, here.  The driver can use phy_read/write  to 
> get/set information anytime it wants.
Is there a user space utility to pull the details from
a GBIC's EEPROM?

Thanks,
Glen

--
 Glen Turner         Tel: (08) 8303 3936 or +61 8 8303 3936
 Australia's Academic & Research Network  www.aarnet.edu.au