netdev - Re: [PATCH v6 1/2] net: mhi: Enable Ethernet interface support

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] [day] [month] [year] [list]

Message-ID: <0235cdaf-4c91-4bb3-9581-9eb24cd1aa47@oss.qualcomm.com>
Date: Mon, 22 Dec 2025 16:13:11 +0530
From: vivek pernamitta <vivek.pernamitta@....qualcomm.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
        "David S. Miller"
 <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
        Manivannan Sadhasivam <mani@...nel.org>, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, mhi@...ts.linux.dev,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v6 1/2] net: mhi: Enable Ethernet interface support



On 12/10/2025 3:08 PM, Jakub Kicinski wrote:
> On Tue, 09 Dec 2025 16:55:38 +0530 Vivek Pernamitta wrote:
>> Add support to configure a new client as Ethernet type over MHI by
>> setting "mhi_device_info.ethernet_if = true". Create a new Ethernet
>> interface named eth%d. This complements existing NET driver support.
>>
>> Introduce IP_SW1, ETH0, and ETH1 network interfaces required for
>> M-plane, NETCONF, and S-plane components.
>>
>> M-plane:
>> Implement DU M-Plane software for non-real-time O-RAN management
>> between O-DU and O-RU using NETCONF/YANG and O-RAN WG4 M-Plane YANG
>> models. Provide capability exchange, configuration management,
>> performance monitoring, and fault management per O-RAN.WG4.TS.MP.0-
>> R004-v18.00.
> 
> Noob question perhaps, what does any of this have to do with Ethernet?
> You need Ethernet to exchange NETCONF messages?

The patch primarily addresses host-to-DU communication. However, the
NETCONF/M-Plane packets originating from the host will eventually be
transmitted from the DU to the RU over the fronthaul, which uses
Ethernet. Bridging is therefore required to forward packets received
from the host towards the fronthaul Ethernet interface.
For additional details on this architecture and data flow, please
refer to the O-RAN Management Plane Specification:

O-RAN.WG4.MP.0-v07.00
O-RAN Alliance Working Group 4 – Management Plane Specification
Chapter 4: O-RU to O-DU Interface Management

-Vivek