netdev - Re: mv88e6321, dual cpu port

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:   Tue, 24 Jan 2023 14:57:03 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Angelo Dureghello <angelo@...nel-space.org>
Cc:     Vladimir Oltean <olteanv@...il.com>, netdev@...r.kernel.org
Subject: Re: mv88e6321, dual cpu port

On Tue, Jan 24, 2023 at 08:21:35AM +0100, Angelo Dureghello wrote:
> 
> Hi Andrew and Vladimir,
> 
> On Mon, 23 Jan 2023, Andrew Lunn wrote:
> 
> > > I don't know what this means:
> > > 
> > > | I am now trying this way on mv88e6321,
> > > | - one vlan using dsa kernel driver,
> > > | - other vlan using dsdt userspace driver.
> > > 
> > > specifically what is "dsdt userspace driver".
> > 
> > I think DSDT is Marvells vendor crap code.
> > 
> Yes, i have seen someone succeeding using it, why do you think it's crap ?

In the Linux kernel community, that is the name given to vendor code,
because in general, that is the quality level. The quality does vary
from vendor to vendor and SDK to SDK, some are actually O.K.

> 
> > Having two drivers for the same hardware is a recipe for disaster.
> > 
> >  Andrew
> > 
> 
> What i need is something as
> 
>         eth0 ->  vlan1 -> port5(rmii)  ->  port 0,1,2
>         eth1 ->  vlan2 -> port6(rgmii) ->  port 3,4
> 
> The custom board i have here is already designed in this way
> (2 fixed-link mac-to-mac connecitons) and trying my best to have
> the above layout working.

With todays mainline i would do:

So set eth0 as DSA master port.

Create a bridge br0 with ports 0, 1, 2.
Create a bridge br1 with ports 3, 4, 6.

You don't actually make use of the br1 interface in Linux, it just
needs to be up. You can think of eth1 being connected to an external
managed switch.

	Andrew