From: Yegor Yefremov <yegorslists@googlemail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Felix Fietkau <nbd@openwrt.org>, Stefan Roese <sr@denx.de>,
netdev <netdev@vger.kernel.org>,
r.meier@siemens.com, lukas.stockmann@siemens.com
Subject: Re: [PATCH] net: phy: Add support for SMSC/Microchip LAN9303 3-port switch
Date: Tue, 11 Mar 2014 16:49:49 +0100 [thread overview]
Message-ID: <CAGm1_kt9eDRtqwL-twLKheW-XMD8RJ7Rmmsbxwdd6EB2NkopOQ@mail.gmail.com> (raw)
In-Reply-To: <CAGVrzcZd7mO6t4eAsn6HVNWFZpPopkBk2trjgSh+3rcWQPHw7g@mail.gmail.com>
Hi Florian,
On Thu, Feb 27, 2014 at 11:21 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> 2014-02-27 14:02 GMT-08:00 David Miller <davem@davemloft.net>:
>> From: Stefan Roese <sr@denx.de>
>> Date: Thu, 27 Feb 2014 10:07:52 +0100
>>
>>> This driver exposes a sysfs interface to access the LAN9303 registers to
>>> userspace. These sysfs files can be used to configure the switch.
>>>
>>> Signed-off-by: Stefan Roese <sr@denx.de>
>>
>> We have an abstraction for programming switch devices called DSA.
>>
>> Even if DSA doesn't fullfill your needs, doing adjustments using sysfs
>> files in userland is going to be the worst user experience possible.
>
> If you remember the discussion that started around the 'swconfig'
> patches, DSA is not suitable for all types of switches, especially not
> those which have no proprietary tagging support (which are about 80%
> of the switches used in embedded systems). That discussion has kind of
> stalled now, so we should probably bring it back...
>
>>
>> Every driver will export different things to tweak, each device will
>> have different semantics and limitations for these settings, etc.
>>
>> Better is to come up with a real, types, interface for programming
>> such devices and providing an implementation of that.
>
> These are definitively the goals of the 'swconfig' patches that were
> posted a while ago, to provide an unified programming API.
> --
> Florian
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Have you tried to apply your swconfig patches to 3.14? There some
compiler errors meanwhile. genl_register_ops() is not available, so
one has to switch to genl_register_family_with_ops() or similar
macros. It would be great, if you could post the updates series and if
possible with ICplus drive included.
Yegor
next prev parent reply other threads:[~2014-03-11 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 9:07 [PATCH] net: phy: Add support for SMSC/Microchip LAN9303 3-port switch Stefan Roese
2014-02-27 22:02 ` David Miller
2014-02-27 22:21 ` Florian Fainelli
2014-03-11 15:49 ` Yegor Yefremov [this message]
2014-02-28 9:32 ` Stefan Roese
2014-02-28 18:00 ` David Miller
2014-03-11 20:11 ` Yegor Yefremov
2014-03-11 20:14 ` Florian Fainelli
2014-03-12 8:47 ` Yegor Yefremov
2014-03-12 8:55 ` Meier, Roger
2014-03-11 20:39 ` David Miller
2014-03-12 8:43 ` Yegor Yefremov
2014-03-12 20:21 ` Ben Hutchings
2014-03-13 22:42 ` Yegor Yefremov
2014-03-14 14:29 ` Ben Hutchings
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=CAGm1_kt9eDRtqwL-twLKheW-XMD8RJ7Rmmsbxwdd6EB2NkopOQ@mail.gmail.com \
--to=yegorslists@googlemail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=lukas.stockmann@siemens.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=r.meier@siemens.com \
--cc=sr@denx.de \
/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).