linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: les stich <stich86@gmail.com>
Cc: "Pali Rohár" <pali@kernel.org>, linux-arm-kernel@lists.infradead.org
Subject: Re: Question abount VSOL/CarlitoxxPro SFP Patch on Marvell Armada (MCBIN DS)
Date: Mon, 9 May 2022 16:47:46 +0100	[thread overview]
Message-ID: <Ynk3orUj/RjGB9XK@shell.armlinux.org.uk> (raw)
In-Reply-To: <dc809ba8-ec64-4ba7-a8e1-60c24bd30296@Spark>

On Mon, May 09, 2022 at 01:09:52PM +0200, les stich wrote:
> Hi Pali,
> 
> no, the stick can do 2.5GbE. Both RTL9601CI and RTL 9601D support HiSGMII mode. I’m currently running another stick (DFP-34X-C2C) at 2.5GbE with my FTTH line here in Italy :)
> 
> the problem seems related only to SFP driver of macchiato-bin, into a BCM57810s, the stick is working as expected ;)

It's entirely possible that the problem is not software, but hardware.
GPON modules have a dying gasp signal on one of the pins, which if
memory serves me correctly, is set to the wrong logic sense on the
SolidRun Clearfog A388 and Macchiatobin platforms.

I seem to remember that the GPON modules I have don't work in either
of these machines for this reason.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
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-09 15:48 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
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) [this message]
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=Ynk3orUj/RjGB9XK@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=pali@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).