linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: marcmicalizzi@gmail.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: MacchiatoBin SingleShot 2500BASE-X port (eth3) with GPON SFP on mvpp2x
Date: Sat, 2 Mar 2019 21:26:29 +0100	[thread overview]
Message-ID: <20190302202629.GB10359@lunn.ch> (raw)
In-Reply-To: <014801d4d121$d2769620$7763c260$@gmail.com>

On Sat, Mar 02, 2019 at 01:00:28PM -0500, marcmicalizzi@gmail.com wrote:
> I’ve just been playing with the mcbin for a little while now, and this
> kernel tree (mcbin branch) seems to be the only way (using a modern kernel)
> I’ve found that actually gets the 10GB SFP ports working on the SingleShot. 
> 
> Unfortunately, however, the GPON SFP I have (Huawei MA5671, provided by my
> ISP) does not seem to work on eth3 (mvpp2x driver). Currently I’m using it
> successfully in a different machine using a Broadcom BCM57810S (bnx2x
> warpcore) with a couple modifications to the driver to link at 2500BASE-X,
> and support SC modules, but was hoping to move it over to the MacchiatoBin
> and try it as a router.
> 
> Worth noting is one quirk of this SFP is that it does not have a physical
> EEPROM, and instead has a soft EEPROM that takes some time to load after
> powering.
 
I've received reports that some GPON SFPs don't like block reads of
their i2c bus. You have to do 16bit word reads.

There was a patch a while ago to deal with i2c bus drivers which could
also not handle big block transfers:

https://www.spinics.net/lists/netdev/msg546524.html

I don't think the comments were every addresses, so it did not get
merged. But you can try reviving the patch, fix it up, and see if
smaller reads help with your problems.

	Andrew

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

  parent reply	other threads:[~2019-03-02 20:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 18:00 MacchiatoBin SingleShot 2500BASE-X port (eth3) with GPON SFP on mvpp2x marcmicalizzi
2019-03-02 18:53 ` Russell King - ARM Linux admin
2019-03-02 20:26 ` Andrew Lunn [this message]
2019-03-03  2:17   ` Marc Micalizzi
2019-03-03  2:48     ` Andrew Lunn
2019-03-03 10:01       ` Russell King - ARM Linux admin
2019-03-03 10:31         ` Russell King - ARM Linux admin
2019-03-03 15:42           ` Marc Micalizzi
2019-03-07 18:42             ` Marc Micalizzi
2019-03-07 19:01               ` Russell King - ARM Linux admin
2019-03-07 19:40                 ` Marc Micalizzi
2019-03-07 22:36                   ` Russell King - ARM Linux admin
2019-03-08 11:09 ` Russell King - ARM Linux admin
2019-03-08 15:09   ` Marc Micalizzi
2019-03-13 15:45     ` Marc Micalizzi
2019-03-14 11:30       ` Russell King - ARM Linux admin
2019-03-14 19:08         ` Marc Micalizzi
2019-03-15  0:22           ` Russell King - ARM Linux admin
2019-03-15  2:18             ` Marc Micalizzi
2019-05-14  1:20               ` Marc Micalizzi

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=20190302202629.GB10359@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marcmicalizzi@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).