Where is the TCP stack handled when using this driver? Is the tcp handled by a higher layer like elsewhere in the kernel, built into the chipset firmware or part of the driver code itself?
I'm trying to use this driver code as a guide to integrating a USB wifi device to an embedded system and I was hoping the chip set might have a built in TCP stack. I've had no luck finding any design documents for a USB wifi device.
The TCP stack is handled by the kernel as it's done for all other network related drivers.
I would rather advise you to read information on http//linuxwireless.org/
, in which may clear some confusion about 'how it's done'.
Don't look straight away into low level drivers without understanding the global picture
My application isn't actually Linux based, its running on a PIC. So I'm pretty much having to redo anything thats not built into the chip if I choose to go with a USB Wifi. I see they've got some reverse engineered specs for various devices, which could help.
Thanks for the help and the quick response.
My thought, you must have a USB host connected to your PIC or your PIC supports USB. You know how your PIC communicates with USB host. Next, You can see the source code from rt2x00 SVN on how to initialize the hardware, upload the firmware, communicate with the baseband processor (bbp) & mac, transfer & recieve the data through USB data. For TCP stack, I think there are a lot of references in Internet. One of them, you can refer http//embedded-system.net/free-tcpip-s ... oller.html
. I also heard that zydas zd1211b also supports UART inside which can attach to external circuit for wireless detection, wireless jammer, etc. Sorry if I'm wrong.