From: Andrew Lunn <andrew@lunn.ch>
To: Ran Shalit <ranshalit@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: cascaded switch
Date: Fri, 18 May 2018 21:13:57 +0200 [thread overview]
Message-ID: <20180518191357.GH23100@lunn.ch> (raw)
In-Reply-To: <CAJ2oMhKDWXG+DjCnMKVGcsmxPG3FscT=SMJQxtSe1=SyqmjMqw@mail.gmail.com>
On Fri, May 18, 2018 at 09:35:38PM +0300, Ran Shalit wrote:
> Hello,
>
> I am trying to understand the concept of cascaded switch.
> I haven't find much information on this topic.
>
> Can anyone please explain the general concept, when is it used, and
> why does the device tree need to know about cascaded switch ?
Hi Ran
I think you first need to define what you mean by cascaded switches.
Andrew
next prev parent reply other threads:[~2018-05-18 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 18:35 cascaded switch Ran Shalit
2018-05-18 19:13 ` Andrew Lunn [this message]
2018-05-18 20:10 ` Ran Shalit
2018-05-18 20:29 ` Andrew Lunn
2018-05-18 20:40 ` Ran Shalit
2018-05-18 20:51 ` Andrew Lunn
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=20180518191357.GH23100@lunn.ch \
--to=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=ranshalit@gmail.com \
/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