From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Ben Hutchings <bhutchings@solarflare.com>
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 22:23:11 +0100 [thread overview]
Message-ID: <20090320212310.GZ4738@xi.wantstofly.org> (raw)
In-Reply-To: <1237583778.3217.4.camel@achroite>
On Fri, Mar 20, 2009 at 09:16:18PM +0000, Ben Hutchings 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.
Yeah, that was intended. On this particular chip model, ports 0-7
are RJ45 ports, 8-9 are SERDES ports, and 10 can either be SERDES or
(R)GMII -- so 10 is a natural choice for the cpu port, 8 and 9 can
be used as interconnect ports to other switches, and 0-7 are used
to connect end-stations to. If there was another switch chip, we
could connect it to port 8 of switch #0.
prev parent reply other threads:[~2009-03-20 21:23 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
2009-03-20 21:23 ` Lennert Buytenhek [this message]
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=20090320212310.GZ4738@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=bhutchings@solarflare.com \
--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