linux-kernel - Re: [PATCH v5 0/5] dt-bindings: net: Add network-class.yaml schema

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]

Message-ID: <3452b67752228665fa275030a7d8100b73063392.camel@sipsolutions.net>
Date: Tue, 25 Mar 2025 11:33:24 +0100
From: Johannes Berg <johannes@...solutions.net>
To: david@...t.cz, Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"	
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski	
 <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Rob Herring
 <robh@...nel.org>,  Krzysztof Kozlowski	 <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Mailing List	
 <devicetree-spec-u79uwXL29TY76Z2rM5mHXA@...lic.gmane.org>, Lorenzo Bianconi
	 <lorenzo@...nel.org>, van Spriel <arend@...adcom.com>, 
 Jérôme Pouiller	 <jerome.pouiller@...abs.com>, Bjorn
 Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>,
 Andy Gross <agross@...nel.org>, Mailing List	
 <devicetree-spec@...r.kernel.org>
Cc: netdev@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, 
	linux-arm-msm@...r.kernel.org, Janne Grunau <j@...nau.net>
Subject: Re: [PATCH v5 0/5] dt-bindings: net: Add network-class.yaml schema

On Mon, 2025-03-24 at 18:41 +0100, David Heidelberg via B4 Relay wrote:
> The Devicetree Specification, Release v0.3 specifies in section 4.3.1
> a "Network Class Binding". This covers MAC address and maximal frame
> size properties. "local-mac-address" and "mac-address" with a fixed
> "address-size" of 48 bits are already in the ethernet-controller.yaml
> schema so move those over.
> 
> Keep "address-size" fixed to 48 bits as it's unclear if network protocols
> using 64-bit mac addresses like ZigBee, 6LoWPAN and others are relevant for
> this binding. This allows mac address array size validation for ethernet
> and wireless lan devices.
> 
> "max-frame-size" in the Devicetree Specification is written to cover the
> whole layer 2 ethernet frame but actual use for this property is the
> payload size. Keep the description from ethernet-controller.yaml which
> specifies the property as MTU.
> 

I have no idea what tree this should go through, and you CC'ed enough
people that I can't figure it out either ... I'll assume not wifi but DT
for now?

johannes