netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Benjamin Beckmeyer <beb@eks-engel.de>
Cc: netdev@vger.kernel.org
Subject: Re: DSA with MV88E6321 and imx28
Date: Thu, 6 Jun 2019 15:59:03 +0200	[thread overview]
Message-ID: <20190606135903.GE19590@lunn.ch> (raw)
In-Reply-To: <e01b05e4-5190-1da6-970d-801e9fba6d49@eks-engel.de>

On Thu, Jun 06, 2019 at 03:47:06PM +0200, Benjamin Beckmeyer wrote:
> 
> On 06.06.19 15:35, Andrew Lunn wrote:
> >> >From our hardware developer I know now that we are using a "mini" SFF 
> >> which has no i2c eeprom. 
> > O.K. Does this mini SFF have LOS, TX-Disable, etc? Are these connected
> > to GPIOs? I assume the SFF is fibre? And it needs the SERDES to speak
> > 1000BaseX, not SGMII?
> 
> Nope, no LOS no tx-disable etc. Yeah, the SFF is fibre. Exactly, it needs 
> SERDES to speak 1000BaseX.

O.K. Then try something like what ZII devel B does:

                                       port@3 {
                                                reg = <3>;
                                                label = "optical3";

                                                fixed-link {
                                                        speed = <1000>;
                                                        full-duplex;
                                                };


What this does not give you is any link monitoring. I don't have the
datasheet of this device, but i assume it has two banks of registers
for the SERDES? And you can get the sync status? Similar to how the
6352 works. But with a fixed link this will be ignored.

> >> Switch				|	external
> >> Port 0 - internal serdes 0x0c --|-------Mini SFF 1x8 Transceiver
> >> 				|
> >> Port 0 - internal serdes 0x0d --|-------Mini SFF 1x8 Transceiver
> >> 				|
> >> Port 2 ----------RGMII----------|-------KSZ9031 PHY 0x02(strap)--Transceiver
> >> 				|
> >> Port 3 - internal PHY 0x03 -----|-------Transceiver
> >> 				|
> >> Port 3 - internal PHY 0x04 -----|-------Transceiver
> >> 				|			
> >> Port 5 - CPU-Port RMII ---------|-------CPU
> >> 				|
> >> Port 6 ----------RGMII----------|-------KSZ9031 PHY 0x06(strap)--Transceiver
> > So the current state is that just the SFF ports are not working? All
> > the copper PHYs are O.K.
> >
> >     Andrew
> >
> The external copper PHYs are still not working properly, but if I set them to
> fixed-link, I see data coming in with I start tcpdump on my device. Just with
> some odd header but I'm not that far with DSA-tags and these stuff.

If you build libpcap & tcpdump from the latest sources, it will
understand these headers.

	Andrew

  reply	other threads:[~2019-06-06 13:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 13:07 DSA with MV88E6321 and imx28 Benjamin Beckmeyer
2019-06-04 13:50 ` Andrew Lunn
2019-06-05  4:52   ` Benjamin Beckmeyer
2019-06-05 12:24     ` Andrew Lunn
2019-06-05 13:12       ` Benjamin Beckmeyer
2019-06-05 13:31         ` Andrew Lunn
2019-06-05 13:54           ` Benjamin Beckmeyer
2019-06-05 18:47             ` Andrew Lunn
2019-06-06  9:39               ` Benjamin Beckmeyer
     [not found]               ` <c27f2b9b-90d7-db63-f01c-2dfaef7a014b@eks-engel.de>
     [not found]                 ` <20190606122437.GA20899@lunn.ch>
2019-06-06 13:27                   ` Benjamin Beckmeyer
2019-06-06 13:35                     ` Andrew Lunn
2019-06-06 13:47                       ` Benjamin Beckmeyer
2019-06-06 13:59                         ` Andrew Lunn [this message]
2019-06-07  9:41                           ` Benjamin Beckmeyer
2019-06-07 12:47                             ` Andrew Lunn
2019-06-11  7:36                               ` Benjamin Beckmeyer
2019-06-11 12:19                                 ` Andrew Lunn
2019-06-11 13:09                                   ` Benjamin Beckmeyer
2019-06-11 13:27                                     ` Andrew Lunn
2019-06-12  9:05                                       ` Benjamin Beckmeyer

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=20190606135903.GE19590@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=beb@eks-engel.de \
    --cc=netdev@vger.kernel.org \
    /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).