From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: "Marek Behún" <kabel@kernel.org>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, olteanv@gmail.com,
pavana.sharma@digi.com
Subject: Re: mv88e6xxx: 2500base-x inband AN is broken on Amethyst? what to do?
Date: Wed, 13 Jan 2021 21:48:00 +0000 [thread overview]
Message-ID: <20210113214800.GM1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210113223729.33c8bb65@kernel.org>
On Wed, Jan 13, 2021 at 10:37:29PM +0100, Marek Behún wrote:
> On Wed, 13 Jan 2021 21:21:25 +0000
> Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote:
> > One thing that I don't know is whether the GPON SFP ONT modules that
> > use 2500base-x will still function with AN disabled - although I have
> > the modules, it appeared that they both needed a connection to the ONU
> > to switch from 1000base-x to 2500base-x on the host side - and as I
> > don't have an ONU I can test with, I have no way to check their
> > behaviour.
>
> We have an ISP here in Prague who is willing to lend us some GPON
> ONU devices to get GPON SFP modules work on Turris. I will ask him if he
> has one capable of 2.5g and try to borrow it.
I know the Huawei MA5671A and the Nokia 3FE46541AA are - see the quirks
table in sfp-bus.c ! They come from an ISP on the American continent
who really really wanted these modules to link at 2.5Gbps.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2021-01-13 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 0:18 mv88e6xxx: 2500base-x inband AN is broken on Amethyst? what to do? Marek Behún
2021-01-13 4:22 ` Marek Behun
2021-01-13 10:28 ` Russell King - ARM Linux admin
2021-01-13 17:03 ` Marek Behún
2021-01-13 20:08 ` Marek Behún
2021-01-13 21:21 ` Russell King - ARM Linux admin
2021-01-13 21:37 ` Marek Behún
2021-01-13 21:48 ` Russell King - ARM Linux admin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210113214800.GM1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=kabel@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pavana.sharma@digi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.