[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87txon3v0l.fsf@dell.be.48ers.dk>
Date: Thu, 07 Mar 2013 19:49:30 +0100
From: Peter Korsgaard <jacmet@...site.dk>
To: Mugunthan V N <mugunthanvnm@...com>
Cc: <netdev@...r.kernel.org>, <davem@...emloft.net>,
<devicetree-discuss@...ts.ozlabs.org>,
<linux-omap@...r.kernel.org>, <b-cousson@...com>, <paul@...an.com>
Subject: Re: [PATCH 1/3] driver: net: ethernet: cpsw: implement ethtool get/set phy setting
>>>>> "Mugunthan" == Mugunthan V N <mugunthanvnm@...com> writes:
Hi,
M> +- ethtool-active-slave : Specifies the slave to use for ethtool command
>>
>> That again sounds like something Linux specific rather than a hardware
>> property.
>>
>> It would be good if all these special things (dual emac mode, vlan
>> handling, switching) could be handled using the existing kernel
>> (bridging/vlan) infrastructure, and the driver always just exposing 2
>> network interfaces instead of these configuration properties.
Mugunthan> Switch and Dual Emac modes of operation of CPSW are two
Mugunthan> different features of the hardware and packet routing
Mugunthan> between the slaves in the hardware are different in both the
Mugunthan> modes.
Mugunthan> If by default it is brought up as Dual EMAC then hardware
Mugunthan> switching is blocked and use-cases like IP phone etc cannot
Mugunthan> be achieved.
Well, you could use the (sw) bridge functionality of the kernel network
stack, but performance naturally wouldn't be as good.
Mugunthan> Since CPSW as a hardware Switch, it cannot not be handled in
Mugunthan> existing kernel feature.
Well, we do have net/dsa, which is conceptually quite similar (even
though it has never been extended to hook into the bridging stuff). I
agree that we don't have infrastructure to handle hw like cpsw in a
really good way today, but it would be very nice to move towards it.
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists