From: Andrew Lunn <andrew@lunn•ch>
To: Guenter Roeck <linux@roeck-us•net>
Cc: davem@davemloft•net, netdev@vger•kernel.org, f.fainelli@gmail•com
Subject: Re: [PATCH 0/2] Indirect phy access for mv88e6171
Date: Sun, 15 Feb 2015 21:25:11 +0100 [thread overview]
Message-ID: <20150215202511.GH3213@lunn.ch> (raw)
In-Reply-To: <54E0E648.8080206@roeck-us.net>
> I'll try. My primary problem right now is that I run Lennert Buytenhek's
> patch set to support bridging offload (aka hardware bridging) on top of
> the upstream dsa code, and the upstream code now supports a competing /
> alternate means to support bridging/switching offload (NET_SWITCHDEV)
> which doesn't work with dsa (at least not yet). So I'll have to figure
> out if / how I can run your patches with my code base, or how I can add
> add support for NET_SWITCHDEV into dsa.
We should be adding switchdev support to DSA for hardware
bridging. The concepts in Lennert Buytenhek's should be a good
starting point for this.
> Do you know if there are any efforts going on in that direction ?
Florian has expressed an interest in getting hardware bridging
working. I've no idea if he has looked at it from the perspective of
switchdev.
Andrew
next prev parent reply other threads:[~2015-02-15 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 18:17 [PATCH 0/2] Indirect phy access for mv88e6171 Andrew Lunn
2015-02-14 18:17 ` [PATCH 1/2] net: dsa: mv88e6352: Refactor shareable code Andrew Lunn
2015-02-16 3:09 ` Guenter Roeck
2015-02-14 18:17 ` [PATCH 2/2] net: dsa: mv88e6171: Enable access to phys via internal mdio bus Andrew Lunn
2015-02-15 18:32 ` [PATCH 0/2] Indirect phy access for mv88e6171 Guenter Roeck
2015-02-15 20:25 ` Andrew Lunn [this message]
2015-02-15 21:05 ` Florian Fainelli
2015-02-15 22:20 ` Guenter Roeck
2015-02-19 20:54 ` David Miller
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=20150215202511.GH3213@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=linux@roeck-us$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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