linux/drivers/staging/ozwpan
Tomas Winkler 07732be2ef staging: ozwpan: fix memcmp() test in oz_set_active_pd()
"addr" is a pointer so it's either 4 or 8 bytes, but actually we want
to compare 6 bytes (ETH_ALEN).

As network stack already provides helper function
is_zero_ether_addr() we use that instead of memcmp

Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Acked-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Rupesh Gujare <rgujare@ozmodevices.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2012-09-04 12:48:00 -07:00
..
Kbuild staging: ozwpan: remove debug allocator 2012-03-02 16:51:09 -08:00
Kconfig staging: ozwpan depends on NET 2012-03-14 12:14:26 -07:00
ozappif.h staging: ozwpan: Correct ioctl numbers. 2012-06-20 16:05:35 -07:00
ozcdev.c staging: ozwpan: fix memcmp() test in oz_set_active_pd() 2012-09-04 12:48:00 -07:00
ozcdev.h staging: ozwpan: Added character device support 2012-02-24 09:26:51 -08:00
ozconfig.h staging: ozwpan: remove debug allocator 2012-03-02 16:51:09 -08:00
ozeltbuf.c staging: ozwpan: remove debug allocator 2012-03-02 16:51:09 -08:00
ozeltbuf.h staging: ozwpan: Added device state support 2012-02-24 09:26:51 -08:00
ozevent.c staging: ozwpan: Replace existing event logging mechanism 2012-04-10 09:40:52 -07:00
ozevent.h staging: ozwpan: Replace existing event logging mechanism 2012-04-10 09:40:52 -07:00
ozeventdef.h staging: ozwpan: Replace existing event logging mechanism 2012-04-10 09:40:52 -07:00
ozhcd.c staging,ozwpan: Fix typo in comments within staging/ozwpan 2012-04-25 10:59:16 -07:00
ozhcd.h staging: ozwpan: Added USB HCD implementation 2012-02-24 09:26:51 -08:00
ozmain.c staging: ozwpan: ISOC transfer in triggered mode 2012-06-20 16:05:34 -07:00
ozpd.c staging: ozwpan: Set AC_VO priority 2012-06-20 16:05:35 -07:00
ozpd.h staging: ozwpan: ISOC transfer in triggered mode 2012-06-20 16:05:34 -07:00
ozproto.c staging: ozwpan: kmalloc flag 2012-06-20 16:05:35 -07:00
ozproto.h
ozprotocol.h staging: ozwpan: ISOC transfer in triggered mode 2012-06-20 16:05:34 -07:00
oztrace.c staging: ozwpan: Added debug support 2012-02-24 09:26:52 -08:00
oztrace.h staging: ozwpan: Added debug support 2012-02-24 09:26:52 -08:00
ozurbparanoia.c staging: ozwpan: Added debug support 2012-02-24 09:26:52 -08:00
ozurbparanoia.h staging: ozwpan: Added debug support 2012-02-24 09:26:52 -08:00
ozusbif.h staging: ozwpan: Added USB service to protocol 2012-02-24 09:26:51 -08:00
ozusbsvc1.c staging: ozwpan: remove debug allocator 2012-03-02 16:51:09 -08:00
ozusbsvc.c staging,ozwpan: Fix typo in comments within staging/ozwpan 2012-04-25 10:59:16 -07:00
ozusbsvc.h staging: ozwpan: Added USB service to protocol 2012-02-24 09:26:51 -08:00
README staging,ozwpan: Fix typo in comments within staging/ozwpan 2012-04-25 10:59:16 -07:00
TODO staging: ozwpan: Update TODO file 2012-06-26 15:07:56 -07:00

OZWPAN USB Host Controller Driver
---------------------------------
This driver is a USB HCD driver that does not have an associated a physical
device but instead uses Wi-Fi to communicate with the wireless peripheral.
The USB requests are converted into a layer 2 network protocol and transmitted
on the network using an ethertype (0x892e) regestered to Ozmo Device Inc.
This driver is compatible with existing wireless devices that use Ozmo Devices
technology.

To operate the driver must be bound to a suitable network interface. This can
be done when the module is loaded (specifying the name of the network interface
as a parameter - e.g. 'insmod ozwpan g_net_dev=go0') or can be bound after
loading using an ioctl call. See the ozappif.h file and the ioctls
OZ_IOCTL_ADD_BINDING and OZ_IOCTL_REMOVE_BINDING.

The devices connect to the host use Wi-Fi Direct so a network card that supports
Wi-Fi direct is required. A recent version (0.8.x or later) version of the
wpa_supplicant can be used to setup the network interface to create a persistent
autonomous group (for older pre-WFD peripherals) or put in a listen state to
allow group negotiation to occur for more recent devices that support WFD.

The protocol used over the network does not directly mimic the USB bus
transactions as this would be rather busy and inefficient. Instead the chapter 9
requests are converted into a request/response pair of messages. (See
ozprotocol.h for data structures used in the protocol).