Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Giammarco lynx <stich86@gmail.com>, linux-arm-kernel@lists.infradead.org
Subject: Re: Question abount VSOL/CarlitoxxPro SFP Patch on Marvell Armada (MCBIN DS)
Date: Sun, 8 May 2022 18:51:59 +0200	[thread overview]
Message-ID: <20220508165159.6jmnbzbvdm34c4qp@pali> (raw)
In-Reply-To: <Yic6vFuEhS7iO7nq@shell.armlinux.org.uk>

On Tuesday 08 March 2022 11:15:08 Russell King (Oracle) wrote:
> I've seen that with some of the other modules (the alcatel/lucent ones)
> where they won't switch to 2.5G unless they are on the PON network and
> have been configured.

Those Alcatel/Lucent GPON SFP modules (including Nokia rebrands) choose
1000base-x vs 2500base-x speed on LAN port based on settings done via
OMCI from OLT.

With advanced OLT you can "force" that speed, even when SFP is already
plugged and running.

So if ISP decide that your LAN port is 1G-only then those Alcatel/Lucent
GPON SFP modules would never switch to 2500base-x mode with user CPU.

Russell, is there any option to ignore speed information stored in SFP
EEPROM and try to choose speed at linux runtime?

And how to correctly handle behavior of SFP module which changes speed
during usage time?

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-08 16:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJbjdrQbAd01WmW-ZQ9d9QKAtUqbQcRkpadtfSH94o9ZUqkhAg@mail.gmail.com>
2022-03-07 16:18 ` Fwd: Question abount VSOL/CarlitoxxPro SFP Patch on Marvell Armada (MCBIN DS) Giammarco lynx
2022-03-07 17:13   ` Russell King (Oracle)
     [not found]     ` <CAJbjdrRiJMnQJEDCABOVxFyaqnSdBbq7Q-ixqBwW2ni49+gfgQ@mail.gmail.com>
     [not found]       ` <YiZZbskbuqq+I2PW@shell.armlinux.org.uk>
     [not found]         ` <CAJbjdrReN4B0XXFFLaTsPj_graAkguQPzP4xtRGbHeGozbJycQ@mail.gmail.com>
2022-03-07 20:12           ` Giammarco lynx
2022-03-07 23:01             ` Russell King (Oracle)
2022-03-08 10:08               ` Giammarco lynx
2022-03-08 11:15                 ` Russell King (Oracle)
2022-03-08 11:54                   ` Giammarco lynx
2022-03-08 12:12                     ` Russell King (Oracle)
     [not found]                       ` <CAJbjdrSRcGVavaWJHuO3_RnP8A30b_ZQS_yAUCUWKCqxrUMwLw@mail.gmail.com>
     [not found]                         ` <Yid39zuckqVLVJts@shell.armlinux.org.uk>
2022-03-08 15:51                           ` Giammarco lynx
2022-05-08 16:51                   ` Pali Rohár [this message]
2022-05-09 15:41                     ` Russell King (Oracle)
2022-05-09 17:08                       ` Pali Rohár
2022-05-09 20:27                         ` Russell King (Oracle)
2022-05-08 16:31               ` Pali Rohár
2022-05-09 11:13                 ` Giammarco lynx
2022-05-09 11:24                   ` Pali Rohár
     [not found]                 ` <dc809ba8-ec64-4ba7-a8e1-60c24bd30296@Spark>
2022-05-09 15:47                   ` Russell King (Oracle)
2022-05-08 16:38             ` Pali Rohár

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=20220508165159.6jmnbzbvdm34c4qp@pali \
    --to=pali@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=stich86@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox