Re: [PATCH] usb: gadget: legacy: ether: fix RNDIS for Windows hosts

[Amine AYAOU]

Thank you for the feedback and for taking the time to review the patch.

It is clear for me now that additions to legacy drivers and RNDIS are
to be avoided.
I have no further arguments for this patch and I don't intend to push
for it further.

For my specific use case, using initramfs is possible (boot time is
unimportant).
Using g_ncm is also an option.

I have answered your questions below for context.

On 10/30/2026 12:13 PM, Greg KH wrote:
> RNDIS should NEVER be used, it's not required by any shipping OS that I
> know of these days, do you?
Windows 10. Specifically, any version prior to Windows 10 1903, where
NCM support was first bundled.

> Why do you want this?  And are you really still using the "legacy" USB
> gadget drivers?  If so, why?  What is preventing you from using the
> "new" ones?
When building a minimalist embedded Linux system, I reached for the most
straightforward option to boot with nfsroot, which happened to be the
legacy drivers.

> useful for which side?  What can you do with this "during boot"?  And
> you are connecting to a nfs windows server with it?
My setup is:
BeagleBone Black (BBB) / Linux <=USB=> Windows <=> WSL (nfs server)
The BBB boots using an nfsroot hosted on the WSL side.
Network traffic goes through Windows.

> What hosts exactly are that?  And why would you connect to them?
As mentioned, versions prior to Windows 10 1903. For instance, Windows
10 Enterprise LTSC 2019.
In a previous strict corporate IT environment, the embedded linux team
were handed Windows 10 machines. They had to connect to Linux (WSL)
through their Windows machines.

> >      Tested on BeagleBone Black with a Windows 11 host
> >      (Version 10.0.26200, Build 26200)
> >      RNDIS automatically bound with the patch.
>
> And did your nfs server on that host work properly?
Yes.
(As mentioned, the nfs server is running on Linux)

Amine Ayaou