[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+h21hpVSzNhYayzF4hfaPiVzLEsxaWPPCrCWhsureRw977jPA@mail.gmail.com>
Date: Wed, 19 Feb 2020 16:18:55 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: "Allan W. Nielsen" <allan.nielsen@...rochip.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Horatiu Vultur <horatiu.vultur@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>,
Joergen Andreasen <joergen.andreasen@...rochip.com>,
Claudiu Manoil <claudiu.manoil@....com>,
netdev <netdev@...r.kernel.org>,
Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH net-next] net: mscc: ocelot: Workaround to allow traffic
to CPU in standalone mode
On Wed, 19 Feb 2020 at 12:11, Allan W. Nielsen
<allan.nielsen@...rochip.com> wrote:
>
> If
> you are certain this is what you want for Felix then lets try find a way
> to make it happend for Felix without chancing the behaivural for Ocelot.
>
I really think this is not the way to go.
As I've explained, you already have the code path in your driver that
I want Felix to operate in.
You just need to put your front-panel port in a bridge, and then
remove it from the bridge. That's it. Whatever your switch does in
that mode, I would like Felix to do it at probe time too. Chances are
that it doesn't bother you, otherwise that code would have been
removed already.
>
> /Allan
>
Thanks,
-Vladimir
Powered by blists - more mailing lists