From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Thomas Subject: Re: SMSC 9303 support Date: Tue, 24 Sep 2013 10:59:30 -0600 Message-ID: <5241C4F2.2040106@mlbassoc.com> References: <524183D6.6040801@mlbassoc.com> <1380041488.2736.41.camel@bwh-desktop.uk.level5networks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Ben Hutchings Return-path: Received: from mail.mlbassoc.com ([65.100.170.105]:39256 "EHLO mail.chez-thomas.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753710Ab3IXQ7c (ORCPT ); Tue, 24 Sep 2013 12:59:32 -0400 In-Reply-To: <1380041488.2736.41.camel@bwh-desktop.uk.level5networks.com> Sender: netdev-owner@vger.kernel.org List-ID: On 2013-09-24 10:51, Ben Hutchings wrote: > On Tue, 2013-09-24 at 06:21 -0600, Gary Thomas wrote: >> I need to support the SMSC9303 in an embedded system. I'm not >> finding any [explicit] support for this device in the latest >> mainline kernel. Did I miss something? >> >> To be clear, the SMSC9303 is a 3-port managed ethernet switch >> capable of supporting 802.1D/802.1Q directly. This switch is >> driven by a single MAC via MII/RMII and exposes the other two >> ports via physical PHYs. What I need it to do is behave like >> two external, separate devices. I was thinking that what I need >> to do is treat these as VLAN devices since the switch can manage >> the routing. >> >> Does this seem like a reasonable approach? > > Linux has 'DSA' (Distributed Switch Architecture) which supports tagging > of packets to indicate which switch port they are sent or received > through. This was originally added to support some Marvell switch chips > and I don't know whether it would be suitable or extensible for this > one. I've used the DSA stuff for years (worked directly with the Marvell folks when it was being developed). It might work for this device, I'll think some more about using it although I was hoping for a lighter weight solution. >> How do I "hook up" my normal ethernet driver to it? To the hardware >> it just looks like any other MII/RMII PHY. The device is managed >> separately via I2C. I can have that set up separately if necessary. >> >> Thanks for any pointers/ideas >> > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------