[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAtXAHc-Rzj41PA8tW6RWROrKDBc_YZWSo1+vvihB5njF_Og-Q@mail.gmail.com>
Date: Thu, 13 Jul 2017 20:36:29 -0700
From: Moritz Fischer <moritz.fischer@...us.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org,
Devicetree List <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 2/2] net: ethernet: nixge: Add support for National
Instruments XGE netdev
Hi Andrew,
On Thu, Jul 13, 2017 at 6:34 PM, Andrew Lunn <andrew@...n.ch> wrote:
>> > > + /* not sure if this is the correct way of dealing with this ... */
>> > > + ndev->phydev->supported &= ~(SUPPORTED_Autoneg);
>> > > + ndev->phydev->advertising = ndev->phydev->supported;
>> > > + ndev->phydev->autoneg = AUTONEG_DISABLE;
>> >
>> > What are you trying to achieve?
>>
>> Basically can't do Autoneg, I'll need to take a closer look.
>
> Hi Moritz
>
> What i actually think you mean, is it can only do 1Gbps. So you could
> autoneg, but only advertise 1Gbps. Look at masking out
> PHY_10BT_FEATURES and PHY_100BT_FEATURES.
It does either 1Gbps or 10Gbps (over SFP+), depending which bitstream is loaded
into the FPGA. In the current setup I could also just have two
different compatible
strings, since neither setup supports the other rate, but that might change.
It seems getting rid of that part (the default values) now works, too.
I'll need to take a closer look tomorrow (and I need to retest with 1Gbps)
>
> Take a look at:
>
> http://elixir.free-electrons.com/linux/latest/source/drivers/net/ethernet/renesas/ravb_main.c#L1045
Will do.
Thanks for feedback,
Moritz
Powered by blists - more mailing lists