linux-kernel - Re: [PATCH v3 net-next 14/24] net: dsa: Introduce driver for NXP SJA1105 5-port L2 switch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 13 Apr 2019 18:46:57 +0300
From:   Vladimir Oltean <olteanv@...il.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Florian Fainelli <f.fainelli@...il.com>, vivien.didelot@...il.com,
        davem@...emloft.net, netdev <netdev@...r.kernel.org>,
        linux-kernel@...r.kernel.org,
        Georg Waibel <georg.waibel@...sor-technik.de>
Subject: Re: [PATCH v3 net-next 14/24] net: dsa: Introduce driver for NXP
 SJA1105 5-port L2 switch

Hi Andrew,

All I'm saying is that at this point in time (patch 14/24), the driver
is being introduced with DSA_TAG_PROTO_NONE. Then support for traffic
and switch tagging is added later on (18/24). I was just explaining
what can be done with the driver up to this point in the patchset.

Thanks,
-Vladimir


On Sat, 13 Apr 2019 at 18:43, Andrew Lunn <andrew@...n.ch> wrote:
>
> On Sat, Apr 13, 2019 at 04:28:12AM +0300, Vladimir Oltean wrote:
> > At this moment the following is supported:
> > * Link state management through phylib
> > * Autonomous L2 forwarding managed through iproute2 bridge commands. The
> >   switch ports are initialized in a mode where they can only talk to the
> >   CPU port. However, IP termination must be done currently through the
> >   master netdevice.
>
> Please could you explain that last sentence in more detail. Normally
> the master device is just a dumb pipe. Nothing, except tcpdump,
> uses it.
>
> Thanks
>
>      Andrew