From: Andrew Lunn <andrew@lunn.ch>
To: John Crispin <blogic@openwrt.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Michael Lee <igvtee@gmail.com>,
Felix Fietkau <nbd@openwrt.org>,
"Steven Liu (?????????)" <steven.liu@mediatek.com>,
"Fred Chang (?????????)" <Fred.Chang@mediatek.com>
Subject: Re: [RFC 5/8] net-next: ralink: add support for rt3050 family
Date: Mon, 23 Nov 2015 00:16:01 +0100 [thread overview]
Message-ID: <20151122231601.GA9582@lunn.ch> (raw)
In-Reply-To: <56521250.1060001@openwrt.org>
> Hi Andrew,
>
> we have had a switch layer inside openwrt called swconfig for several
> years. at the moment i have an add-on patch in openwrt to provide an
> userland interface via that layer.
Hi John
I know of swconfig. However, it has been NACKed for mainline. So you
either need to do switchdev or DSA for controlling switches in
mainline.
Andrew
next prev parent reply other threads:[~2015-11-22 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 8:40 [RFC 1/8] Documentation: DT: net: add docs for ralink/mediatek SoC ethernet binding John Crispin
2015-11-22 8:40 ` [RFC 2/8] net-next: phy: dont auto handle carrier state when multiple phys are attached John Crispin
2015-11-24 18:42 ` Florian Fainelli
2015-11-22 8:40 ` [RFC 3/8] net-next: ralink: add the drivers core files John Crispin
2015-11-22 8:40 ` [RFC 4/8] net-next: ralink: add support for rt2880 John Crispin
2015-11-22 8:40 ` [RFC 5/8] net-next: ralink: add support for rt3050 family John Crispin
2015-11-22 16:36 ` Andrew Lunn
2015-11-22 19:06 ` John Crispin
2015-11-22 23:16 ` Andrew Lunn [this message]
2015-11-23 6:47 ` John Crispin
2015-11-22 8:40 ` [RFC 6/8] net-next: ralink: add support for rt3883 John Crispin
2015-11-22 8:40 ` [RFC 7/8] net-next: ralink: add support for mt7620 family John Crispin
2015-11-22 8:40 ` [RFC 8/8] net-next: ralink: add Kconfig and Makefile John Crispin
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=20151122231601.GA9582@lunn.ch \
--to=andrew@lunn.ch \
--cc=Fred.Chang@mediatek.com \
--cc=blogic@openwrt.org \
--cc=davem@davemloft.net \
--cc=igvtee@gmail.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=steven.liu@mediatek.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).