Hi There,
Since Linux is preparing to disable drivers for Microsoft’s RNDIS protocol, what will be the alternative on the beaglebone USB network connectivity?
P.S. kernel/git/gregkh/usb.git - USB development tree
Best Regards,
Nikolay
Ugh.
@koleto technically, we’ve been shipping the alternative for a few years now…
Every BeagleBoard.org image has two usb network end points, RNDIS and NCM. Only Apple/Linux have been actively using NCM.
What we need on Windows… Either figure out how Windows will load the NCM driver automatically, or a (yuck) figure out a self-signed Windows NCM driver to load it…
Any Windows developers i’m all hears, we tried this once before and it failed as the cert never got resigned… So we need a Docker/CI/etc image that’ll do re-signing every month or something setup in our gitlab ci…
Edit, side note, timelines using TI’s BSP kernel tree…
Shipping v5.10.x-ti today
Shipping v6.1.x-ti (this fall, next summer)…
Fingers crossed that commit will either hit 6.6.x or 6.7.x, this may affect the default image in 2 summers…
Edit 2:
Ugh: NCM drivers officially shipped with Windows 11 what about 10/8/7 Microsoft!!!
Regards,
So… @jkridner on Windows 11…
NCM just works… (no 3rd party driver, no nothing, just plugin…)
So we need to build and sign GitHub - microsoft/NCM-Driver-for-Windows: The Windows NCM drivers (host-side and function-side) are the NetAdapterCx based NIC drivers that implements Network Control Model (CDC NCM) specification defined by USB-IF for Windows 7, 8, 10…
Regards,
2 Likes
Side thought… Since Debian 12.x bookworm release is still really new… do we force only NCM on Debian 12.x + , and thus get the community help us make a signed driver… Or wait till Debian 13.x (2 summers)…
@RobertCNelson thank you for your response. I also saw the in the ncm.usb0 configuration in /usr/bin/bb-start-usb-gadgets, which works perfectly on MacOS. It seems like only Windows 10 will be a problem, but U never knows… I have to verify this when I get some time and will let U know.
Best Regards,
@koleto