Just use an older kernel that includes RNDIS if you need that. No one can force an update to get support because--ha, ha, ha--it's open source and there wasn't any support in the first place.Can't recall entirely but that might be illustrative of the problem. The Pi appears as 'cdc_ether' by default, Linux is fine with that, but Windows says 'No idea, that needs to be RNDIS if you want me to work with it. Error 10'.The command lsusb -t reports ... Class=CDC Data, Driver=cdc_ether ... for the Pi Zero running here as a USB Ethernet gadget. Hopefully removing RNDIS will not make any difference when connecting to a Zero.
So you spend ages figuring out how to make the Pi present RNDIS, but once you have done so it works with Windows. And Linux too because that supports RNDIS. Yay!
Or did.
What if you bought a product which presents as RNDIS, used to work on Linux and Windows, what do you do with it if Linux drops support for RNDIS ... bin it, junk Linux in favour of Windows ?
"2024 - Year of the Linux Landfill"
Seriously though, Red Hat will support the 3.10 kernel until 2028 and that kennel was released in June 2013. If a similar schedule is followed for recent kernels, then everything should be fine until 2039 after which the one remaining person may have to provide their own RNDIS support as everyone else will have been assimilated into a global ChatGPT-style AI.
Statistics: Posted by ejolson — Fri Jan 12, 2024 1:49 am