> -----Original Message-----
> From: Kumar Gala [mailto:ga...@kernel.crashing.org]
> Sent: Tuesday, August 11, 2009 7:11 PM
> To: Aggrwal Poonam-B10812
> Cc: linuxppc-...@ozlabs.org
> Subject: Re: [v3][PATCH][powerpc/85xx] P2020RDB Platform Support Added
>
>
> On Aug 7, 2009, at 10:35 AM, Poonam Aggrwal wrote:
>
> >
> > + enet2: ether...@26000 {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + cell-index = <2>;
> > + device_type = "network";
> > + model = "eTSEC";
> > + compatible = "gianfar";
> > + reg = <0x26000 0x1000>;
> > + ranges = <0x0 0x26000 0x1000>;
> > + local-mac-address = [ 00 00 00 00 00 00 ];
> > + interrupts = <31 2 32 2 33 2>;
> > + interrupt-parent = <&mpic>;
> > + phy-handle = <&phy1>;
> > + phy-connection-type = "rgmii-id";
> > + };
>
> was there an answer to why we don't have an mdio node for enet2?
>
Yes I already replied to it, actually the enet2 (eTSEC3) on RDB is only
exposed as RGMII, and the mdio lines it will use is those of enet0. In
case it also could be configured in SGMII(as in P2020DS), then we would
have needed the mdio node for enet2 to configure the TBI PHY.
> - k
>
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
