>The closed nature of the USXGMII spec makes it very hard for us to know
>whether your implementation is correct or not.
>
>I have some documentation which suggests that USVGMII is a USXGMII link
>running at "5GR" rate as opposed to USXGMII running at "10GR" rate.
>
>So, I think 5G mode should be l
On Tue, Jun 25, 2019 at 08:26:29AM +, Parshuram Raju Thombare wrote:
> Hi Andrew,
>
> >What i'm saying is that the USXGMII rate is fixed. So why do you need a
> >device
> >tree property for the SERDES rate?
> This is based on Cisco USXGMII specification, it specify USXGMII 5G and
> USXGMII 1
Hi Andrew,
>What i'm saying is that the USXGMII rate is fixed. So why do you need a device
>tree property for the SERDES rate?
This is based on Cisco USXGMII specification, it specify USXGMII 5G and USXGMII
10G.
Sorry I can't share that document here.
Regards,
Parshuram Thombare
On Mon, Jun 24, 2019 at 06:52:51AM +, Parshuram Raju Thombare wrote:
> Hi Andrew,
>
> >> +enum {
> >> + MACB_SERDES_RATE_5_PT_15625Gbps = 5,
> >> + MACB_SERDES_RATE_10_PT_3125Gbps = 10,
> >> +};
> >What do the units mean here? Why would you clock the SERDES at 15Tbps,
> >or 3Tbps? 3.125Mbps
Hi Andrew,
>> +enum {
>> +MACB_SERDES_RATE_5_PT_15625Gbps = 5,
>> +MACB_SERDES_RATE_10_PT_3125Gbps = 10,
>> +};
>What do the units mean here? Why would you clock the SERDES at 15Tbps,
>or 3Tbps? 3.125Mbps would give you 2.5Gbps when using 8b/10b encoding.
>
MACB_SERDES_RATE_5_PT_15625Gbps
> +enum {
> + HS_MAC_SPEED_100M,
> + HS_MAC_SPEED_1000M,
> + HS_MAC_SPEED_2500M,
> + HS_MAC_SPEED_5000M,
> + HS_MAC_SPEED_1M,
> + HS_MAC_SPEED_25000M,
> +};
> +
> +enum {
> + MACB_SERDES_RATE_5_PT_15625Gbps = 5,
> + MACB_SERDES_RATE_10_PT_3125Gbps = 10,
> +};
Wh
6 matches
Mail list logo
