linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* [RFC] (re)describing the PHY interface property
@ 2007-03-09  3:07 Kim Phillips
  2007-03-09 23:52 ` Andy Fleming
  0 siblings, 1 reply; 2+ messages in thread
From: Kim Phillips @ 2007-03-09  3:07 UTC (permalink / raw)
  To: linuxppc-dev

we need to fix the interface property of the PHY nodes in the device
trees.  currently, we see things such as:

	interface = <6>; //ENET_1000_GMII

in mpc836x_mds.dts, which is bad because the speed and interface type
are conjoined.  I found a spec proposal based on response to a similar
matter on this list:

	http://playground.sun.com/1275/proposals/Closed/Accepted/378-it.txt

So do we go with proposal #378, and add the interface type to the end of
its comma-separated list, like this:

	supported-network-type = "ethernet,1000,,full,gmii";

or forget about proposal #378, and do something like:

	max-speed = <d#1000>;
	interface-type = "gmii";

?

Kim

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [RFC] (re)describing the PHY interface property
  2007-03-09  3:07 [RFC] (re)describing the PHY interface property Kim Phillips
@ 2007-03-09 23:52 ` Andy Fleming
  0 siblings, 0 replies; 2+ messages in thread
From: Andy Fleming @ 2007-03-09 23:52 UTC (permalink / raw)
  To: Kim Phillips; +Cc: linuxppc-dev


On Mar 8, 2007, at 21:07, Kim Phillips wrote:

> we need to fix the interface property of the PHY nodes in the device
> trees.  currently, we see things such as:
>
> 	interface = <6>; //ENET_1000_GMII
>
> in mpc836x_mds.dts, which is bad because the speed and interface type
> are conjoined.  I found a spec proposal based on response to a similar
> matter on this list:
>
> 	http://playground.sun.com/1275/proposals/Closed/Accepted/378-it.txt
>
> So do we go with proposal #378, and add the interface type to the  
> end of
> its comma-separated list, like this:
>
> 	supported-network-type = "ethernet,1000,,full,gmii";


While I don't object to the supported/chosen IEEE addition, your  
proposal is to modify it into a realm I'm not convinced it was meant  
to address.  The properties described in their proposal all clearly  
relate to the connection between the PHY device and the actual medium  
through which the signal propagates.

The issue at hand is the connection between the PHY and the MAC,  
which is quite different.  Mostly because we do not currently have  
any code that cares about the transceiver, but the network won't work  
if the interface is not configured properly.



>
> or forget about proposal #378, and do something like:
>
> 	max-speed = <d#1000>;
> 	interface-type = "gmii";


I'm ok with this.  I'm not sure you even need the "-type" at the end.

Andy

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-03-09 23:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-09  3:07 [RFC] (re)describing the PHY interface property Kim Phillips
2007-03-09 23:52 ` Andy Fleming

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).