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

[Manivannan Sadhasivam]

On Mon, Dec 22, 2025 at 04:13:11PM +0530, vivek pernamitta wrote:
> 
> 
> 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:
> 

You missed one obvious point. The actual link between the device (QDU100) and
the host is PCIe/MHI. The device has the Etherent inteface and is exposed as the
MHI channel to the host. So this patch creates the Ethernet interface on the
host based on the 'IP_ETH' channel so that the host can use this interface for
exchaning the NETCONF packets.

All the rest of the O-RAN management details are irrelevant.

- Mani

-- 
மணிவண்ணன் சதாசிவம்