On Wed, Apr 09, 2008 at 10:25:29AM +0200, Indan Zupancic wrote: > On Wed, April 9, 2008 01:59, John W. Linville wrote: > > On Wed, Apr 09, 2008 at 12:07:37AM +0200, Indan Zupancic wrote: > >> Quoting the HFA3842B datasheet: > >> > >> "The USB host port interface uses Microsoft's Remote NDIS > >> protocol to communicate with the network software on the > >> host computer." > > > > The datasheets I found for that don't seem to have that quote...? > > It's on page 21 of the HFA3842B datasheet, June 2001, File Number 8020 > version. I also found on page 23: "Complete details on the USB firmware > for controlling this port can be obtained by contacting the factory directly." > > Could be that I'm looking at the wrong datasheet, mind you. Ah, I see it now -- I must have been searching for "RNDIS" instead of "Remote NDIS" -- oops! > > Well, the good news is that RNDIS wireless devices will be supported > > in 2.6.26 via the new rndis_wlan driver. :-) However, I don't think > > that all Prism2 USB devices are RNDIS. > > RNDIS seems to define the way data is exchanged, but not the format > or meaning of the data itself, so it needs its own driver anyway. At least > that's my impression. It's a bit vague, but I didn't read the specification. AFAIK, RNDIS is just a means of packaging the NDIS driver API so that the driver functions are performed remotely across the USB bus. Specific NDIS OIDs perform the same task for an RNDIS device as they would in a call to a normal NDIS driver (such as on Windows or within NDISwrapper). A single RNDIS driver should work with any number of different RNDIS devices. I don't know whether this specific device support RNDIS or not. Experience reading vendor datasheets suggest to me that the datasheet author only surmised that the device would be use to build RNDIS devices. Whether or not that turned-out to be true is anyone's guess. :-) John -- John W. Linville linville at tuxdriver.com
