Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, Gary Thomas <gary@mlbassoc.com>,
	Jesper Dangaard Brouer <hawk@diku.dk>
Subject: Re: [PATCH 3/3] dsa: add switch chip cascading support
Date: Fri, 20 Mar 2009 21:16:18 +0000	[thread overview]
Message-ID: <1237583778.3217.4.camel@achroite> (raw)
In-Reply-To: <20090320195209.GW4738@xi.wantstofly.org>

On Fri, 2009-03-20 at 20:52 +0100, Lennert Buytenhek wrote:
[...]
> For the example topology above, the dsa platform data would look
> something like this:
> 
> 	static struct dsa_chip_data sw[2] = {
> 		{
> 			.mii_bus	= &foo,
> 			.sw_addr	= 1,
> 			.port_names[0]	= "p1",
> 			.port_names[1]	= "p2",
> 			.port_names[2]	= "p3",
> 			.port_names[3]	= "p4",
> 			.port_names[4]	= "p5",
> 			.port_names[5]	= "p6",
> 			.port_names[6]	= "p7",
> 			.port_names[7]	= "p8",
> 			.port_names[9]	= "dsa",
> 			.port_names[10]	= "cpu",
> 			.rtable		= (s8 []){ -1, 9, },
[...]

Is there supposed to be a gap in the numbering here?  The diagram above
seemed to number the ports 1-10 but I'm guessing the internal numbering
of those would be 0-9.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
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:[~2009-03-20 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 19:52 [PATCH 3/3] dsa: add switch chip cascading support Lennert Buytenhek
2009-03-20 21:16 ` Ben Hutchings [this message]
2009-03-20 21:23   ` Lennert Buytenhek

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=1237583778.3217.4.camel@achroite \
    --to=bhutchings@solarflare.com \
    --cc=buytenh@wantstofly.org \
    --cc=davem@davemloft.net \
    --cc=gary@mlbassoc.com \
    --cc=hawk@diku.dk \
    --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