Received-SPF: pass (google.com: domain of linux-kernel+bounces-161992-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon, 29 Apr 2024 11:32:17 +0200
From: Lukasz Majewski <lukma@denx.de>
To: Casper Andersson <casper.casan@gmail.com>
Cc: netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>, Andrew Lunn
 <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>, Vladimir Oltean
 <olteanv@gmail.com>, "David S. Miller" <davem@davemloft.net>, Jakub
 Kicinski <kuba@kernel.org>, Oleksij Rempel <o.rempel@pengutronix.de>,
 Tristram.Ha@microchip.com, Sebastian Andrzej Siewior
 <bigeasy@linutronix.de>, Ravi Gunasekaran <r-gunasekaran@ti.com>, Simon
 Horman <horms@kernel.org>, Nikita Zhandarovich <n.zhandarovich@fintech.ru>,
 Murali Karicheri <m-karicheri2@ti.com>, Jiri Pirko <jiri@resnulli.us>, Dan
 Carpenter <dan.carpenter@linaro.org>, Ziyang Xuan
 <william.xuanziyang@huawei.com>, Shigeru Yoshida <syoshida@redhat.com>,
 "Ricardo B. Marliere" <ricardo@marliere.net>, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v5 1/4] net: hsr: Provide RedBox support
 (HSR-SAN)
Message-ID: <20240429113217.0fb8d6d7@wsk>
In-Reply-To: <8634rho41l.fsf@gmail.com>
References: <20240415124928.1263240-1-lukma@denx.de>
	<20240415124928.1263240-2-lukma@denx.de>
	<86mspt7glf.fsf@gmail.com>
	<20240416150359.7362c762@wsk>
	<86bk66hjyf.fsf@gmail.com>
	<20240418173706.206e6a2f@wsk>
	<86mspploa3.fsf@gmail.com>
	<20240419124223.2388295d@wsk>
	<8634rho41l.fsf@gmail.com>
Organization: denx.de
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/C6CorqEZXRzDpTNmg9+Lr3=";
 protocol="application/pgp-signature"; micalg=pgp-sha512

--Sig_/C6CorqEZXRzDpTNmg9+Lr3=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Casper,

> >
> > Hmm... I'm wondering how "proxy" is implemented then.
> > Also, what is the purpose of ProxyNodeTable in that case? =20
>=20
> The ProxyNodeTable becomes the same as the MAC table for the interlink
> port. I.e. normal MAC learning, when a frame is sent by a SAN and
> received on interlink the HW learns that that SMAC is on the interlink
> port (until it ages out).=20

+1

> This table can be read out and used for
> supervision frames.
>=20

I've go through the standard again and it looks like it is mandatory
for RedBox to send supervisory frames with MAC addresses from
ProxyNodeTable as its payload. Moreover, the RedBox MAC address shall
be also send as the second (i.e. following) payload in this frame.

The current RedBox (from net-next) needs to be extended to support it
 - I've started working on this.

> Though, the NodesTable I don't think is used in HW. As I understand
> it's an optional feature.

+1


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

--Sig_/C6CorqEZXRzDpTNmg9+Lr3=
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEgAyFJ+N6uu6+XupJAR8vZIA0zr0FAmYvaSEACgkQAR8vZIA0
zr2klgf9FsTRrBZ8kpx4smbAThax9QN7aEiGWidRjn19R88sc8gDaGp0I3DCWs/c
uGcLx/7VwFQwjj5FqCxfwWbus7+1Wo3B67dNU62U0TCpN9fqtKeHLFNgtjqStrOO
Q8E3g+pWwvTQFar+FTOSAzmExX4R7eK3BAlq8bFsTT4nd3ET030lVRa/sisDOhWi
RMWHKCea7svwuOYV45dYwzlfXdu0hx8Y7cGUHBmbp8zxcfKN+MJa+ktWwdqNgUPn
xAGGvo4IAzluqbzjNZjaeok1uML4nw8Vm6g/FigO0fM1JylKawhwyy9HpxZhh0jF
zxo+jvH+MSVrvg4Hsh1AzWUUeyqfww==
=H3gL
-----END PGP SIGNATURE-----

--Sig_/C6CorqEZXRzDpTNmg9+Lr3=--