Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: SMSC 9303 support
Date: Tue, 24 Sep 2013 17:51:28 +0100	[thread overview]
Message-ID: <1380041488.2736.41.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <524183D6.6040801@mlbassoc.com>

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.

Ben.

> 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
> 

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2013-09-24 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 12:21 SMSC 9303 support Gary Thomas
2013-09-24 16:51 ` Ben Hutchings [this message]
2013-09-24 16:59   ` Gary Thomas
2013-09-24 18:29     ` Florian Fainelli
2013-09-24 19:13       ` Gary Thomas
2013-09-25  8:24         ` Florian Fainelli

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=1380041488.2736.41.camel@bwh-desktop.uk.level5networks.com \
    --to=bhutchings@solarflare.com \
    --cc=gary@mlbassoc.com \
    --cc=netdev@vger.kernel.org \
    /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