Netdev List
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org,
	Egil Hjelmeland <privat@egil-hjelmeland.no>,
	Andrew Lunn <andrew@lunn.ch>,
	Juergen Borleis <jbe@pengutronix.de>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	lorenzo@kernel.org
Subject: Re: DSA using cpsw and lan9303
Date: Wed, 16 Feb 2022 19:55:43 +0200	[thread overview]
Message-ID: <20220216175543.l6smw26vl4qencau@skbuf> (raw)
In-Reply-To: <yw1xy22a1z63.fsf@mansr.com>

On Wed, Feb 16, 2022 at 05:47:32PM +0000, Måns Rullgård wrote:
> The LAN9303 has (R)MII for port 0 and internal PHYs for ports 1/2, so
> there's really only one sensible way to connect it, even though the
> switch core has identical functionality for all ports.

As strange as it may seem to you, people are connecting other switches
to a Beaglebone Black and using one of the internal PHY ports as a CPU
port. That driver did not need any modification for that particular
aspect (the port number), even though that use case was not directly planned:
https://patchwork.kernel.org/project/netdevbpf/patch/20210814025003.2449143-11-colin.foster@in-advantage.com/#24380929

      reply	other threads:[~2022-02-16 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 16:44 DSA using cpsw and lan9303 Måns Rullgård
2022-02-14 17:16 ` Florian Fainelli
2022-02-14 17:43   ` Vladimir Oltean
2022-02-14 19:17     ` Måns Rullgård
2022-02-15 20:54   ` Vladimir Oltean
2022-02-16 13:17     ` Måns Rullgård
2022-02-16 14:15       ` Vladimir Oltean
2022-02-16 14:23         ` Måns Rullgård
2022-02-16 14:26           ` Vladimir Oltean
2022-02-16 17:00             ` Vladimir Oltean
2022-02-16 17:47               ` Måns Rullgård
2022-02-16 17:55                 ` Vladimir Oltean [this message]

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=20220216175543.l6smw26vl4qencau@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=jbe@pengutronix.de \
    --cc=lorenzo@kernel.org \
    --cc=mans@mansr.com \
    --cc=netdev@vger.kernel.org \
    --cc=privat@egil-hjelmeland.no \
    /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