From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
netdev <netdev@vger.kernel.org>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: dsa: using multi-gbps speeds on CPU port
Date: Thu, 16 May 2019 14:58:00 +0200 [thread overview]
Message-ID: <20190516125800.GC14298@lunn.ch> (raw)
In-Reply-To: <CA+h21hp5aX00jtj5bSkig1jGY8JHAsKwGp+584jbOw3k82Z5KA@mail.gmail.com>
> My basic idea is to interface a Raspberry Pi-like board to a dumb
> "switch evaluation board" which has only the Ethernet ports and the
> SPI/whatever control interface exposed. The DSA CPU/master port combo
> in this case would go through a Cat5 cable, which is not going to pan
> out very well currently because both the RPi-side PHY and the switch
> board-side PHY need some massaging from their respective drivers. Both
> PHYs are C22.
Hi Vladimir
There are a number of boards like this, back to back PHYs. But they
all have the switch PHY strapped so they start on power on and
auto-negotiate. DSA then just works.
Andrew
next prev parent reply other threads:[~2019-05-16 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 12:39 dsa: using multi-gbps speeds on CPU port Maxime Chevallier
2019-05-15 13:27 ` Andrew Lunn
2019-05-15 14:02 ` Maxime Chevallier
2019-05-15 16:09 ` Florian Fainelli
2019-05-15 16:19 ` Russell King - ARM Linux admin
2019-05-16 6:56 ` Vladimir Oltean
2019-05-16 12:58 ` Andrew Lunn [this message]
2019-05-17 15:10 ` Maxime Chevallier
2019-05-17 17:37 ` Ioana Ciornei
2019-05-17 18:03 ` Russell King - ARM Linux admin
2019-05-17 18:10 ` Florian Fainelli
2019-05-17 18:23 ` Russell King - ARM Linux admin
2019-05-15 16:12 ` Russell King - ARM Linux admin
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=20190516125800.GC14298@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vivien.didelot@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 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.