Re: [ANNOUNCE] RNDIS Gadget Driver
From: Robert Schwebel
Date: Fri Mar 26 2004 - 11:37:38 EST
On Fri, Mar 26, 2004 at 07:58:04AM -0800, David Brownell wrote:
> >>>- .bDeviceClass = DEV_CONFIG_CLASS,
> >>>+ .bDeviceClass = 0x02,
> >>Is this wise?
> >Until now DEV_CONFIG_CLASS was 0xFF, which results in Windows getting
> >hickup. If you directly set this to 0x02 (Network Device) Win is happy.
> Actually I suspect setting it to USB_CLASS_COMM would be preferred, in
> RNDIS-specific config descriptors....
We have tried that, Windows does not like it. The only constellation
where it worked was setting the device descriptor's bConfigClass=0x02.
RNDIS is a sensitive beast. Do one bit different results in that uggly
"Error 10" message on the Windows side. We saw it when we started with
the driver, we saw it when the driver was half way finished and we will
see it again if somebody tweaks the driver without exactly knowing what
the guys at Microsoft smoked when they designed that protocol :-)
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hornemannstraße 12, 31137 Hildesheim, Germany
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/