On Fri, Feb 3, 2023 at 7:56 AM Janne Grunau <j@xxxxxxxxxx> 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 is already in the ethernet-controller.yaml > schema so move those over. > I think the only commonly used values for address-size are 48 and 64 > bits (EUI-48 and EUI-64). Unfortunately I was not able to restrict the > mac-address size based on the address-size. This seems to be an side > effect of the array definition and I was not able to restrict "minItems" > or "maxItems" based on the address-size value in an "if"-"then"-"else" > block. > An easy way out would be to restrict address-size to 48-bits for now. I've never seen 64-bits used... > I've ignored "max-frame-size" since the description in > ethernet-controller.yaml claims there is a contradiction in the > Devicetree specification. I suppose it is describing the property > "max-frame-size" with "Specifies maximum packet length ...". Please include it and we'll fix the spec. It is clearly wrong. 2 nios boards use 1518 and the consumer for them says it is MTU. Everything else clearly uses mtu with 1500 or 9000. > My understanding from the dt-schema README is that network-class.yaml > should live in the dt-schema repository since it describes properties > from the Devicetree specification. How is the synchronization handled in > this case? The motivation for this series is to fix dtbs_check failures > for Apple silicon devices both in the tree and upcoming ones. Let's add it to the kernel, then later we can copy it to dtschema, bump the minimum version the kernel requires, and delete the kernel copy. Rob
